From MediaWiki.org
Jump to navigation Jump to search
This page is a translated version of the page Manual:Short URL and the translation is 35% complete.

Other languages:
Deutsch • ‎English • ‎español • ‎français • ‎日本語 • ‎한국어 • ‎polski • ‎português • ‎português do Brasil • ‎русский • ‎中文

缩短的URLURL重写会使页面地址中隐藏php文件扩展名。 在开始之前,请花几分钟时间为您的网站设计一个“稳定的URL结构”,以减少问题。




/var/www/localhost/htdocs/mediawiki/w (用Root账户安装)
/home/johndoe/public_html/mediawiki/w (虚拟主机安装)


http://example.org/w/index.php/Page_title (Mediawiki的最新版本,无CGI支持)
http://example.org/w/index.php?title=Page_title (Mediawiki的最新版本,有CGI支持)

使用下面将提到的方法, 我们可以把地址设置成下面的样子:

http://example.org/wiki/Page_title 这是最常见的配置,维基百科也采用同样的配置,但不是缺省值,因为它需要配置服务器。
http://example.org/Page_title (不推荐使用!参见下方)
http://wiki.example.org/Page_title (不推荐使用!参见下方)
Having the page name right in the root of the domain name is not recommended, because it will conflict with files and directories located at the root directory. 例如,如果你有一个图像文件存放在“/images/”目录下,那么你无法在维基里命名一个页为“Images”。


  • 优势:缩短URL会对终端用户隐藏大部分技术细节,这对大部分站点拥有者都是有用的。除此之外,这还意味着当底层软件变动时可以保持url的稳定性。 (See above for the difference between MediaWiki's default URL structure with CGI enabled vs without). 对访问者来说,他们也更易于记忆并且让访问者更方便的根据URL进行导航。 Additionally, short URLs offer an advantage over the default URLs for w:Search engine optimization, as URLs containing ? can be treated less favorably by search engines when calculating page rank.
  • Disadvantage: Requires configuration, so, depending on the hosting environment you are using, it might be difficult to recreate. However, as every widely used webserver is capable of being configured to use short URLs, most paid web hosting services should support this feature. Any host that doesn't offer you this feature is not worth your money.


Our official guides for short URL configuration for different web servers. Pick your webserver's configuration from this list. If you don't know what server software you are using, then it is most likely Apache.


These guides are old and are almost entirely bad advice. These will eventually be deleted one by one as our official guides above are created for different webservers.

Anyone is welcome to create a how-to solution page and list it below. Please use a sensible name for the page, one that fits in with the below names. When each unique solution has its own page, readers can skip complexity they do not want. Keep it simple, readable, short, with a separate page per separate solution.

To help others find out which Short URL methods really work, after trying each method please edit the page and increase the "worked" or "didn't_work" numbers for that guide and make a brief (or long, your choice) description on what went wrong by clicking the link on your number.


Actions such as edit, view history, etc. will still have index.php unless $wgActionPaths are defined.


These methods require that you have access to the server configuration. If you are on a shared host, you most likely don't. In this case you will be required to use a method that requires "no root access". You can jump directly to the MediaWiki ShortURL Builder tool and follow the on screen instructions after clicking on "I don't have root access".

* Abyss Web Server X2

(for Apache guidance, see the link in the Guides section).


如何创建example.com/Page_title URL:


如何创建wiki.example.com/Page_title URL。



The ampersand problem shows up when you have page titles with symbols in (such as &, ?, #, + and /) that, despite being correctly encoded in the link are not being passed correctly from mod_rewrite to the script. This manifests in 404 page-not-found errors, because the title gets cut off at the special character. For example, clicking on a link to "John & Maria's page" gets a 404, because MediaWiki is looking for a page named "John ".

This is because ampersands in long-form names are treated as query string separators, and would never reach the PHP runtime environment. This is caused by an old and problematic mod_rewrite bug.[1]


This issue is caused by the ?title=$1 portion of rewrite rules like /index.php?title$1 which is completely unnecessary and harmful. MediaWiki parses paths directly from the REQUEST_URI so rewrite everything to /index.php.


With Ubuntu 8.10 and MediaWiki 1.11.2 (and maybe later versions) if you use the MediaWiki sanctioned directions your skins may fail to load. To fix this, create a symbolic link in /var/www pointing to /var/lib/mediawiki with the value of $wgScriptPath in LocalSettings.php. If, for example, $wgScriptPath is set to "/w" then you need to run the command "sudo ln -s /var/lib/mediawiki /var/www/w".

Alternatively, try setting $wgLoadScript to the original file. If you source url is /wiki with the short url /w, set it to /wiki/load.php.


If you notice that your changes to $wgArticlePath in LocalSettings.php are not being reflected in mysite.com/wiki/Main_Page, it may be due MediaWiki's caching of the links according to previous settings.

Go to mysite.com/wiki/Main_Page?action=purge to force MediaWiki to regenerate the cached links.


  1. execute the MySQL query "TRUNCATE objectcache;", or
  2. Ensure $wgCacheEpoch is updated (if $wgInvalidateCacheOnLocalSettingsChange is enabled all you have to do is edit LocalSettings.php to purge it)


Our official guides for short url configuration include recommendations on how to point the root of your site to your wiki using your short url config.

For example our Apache guide recommends using this to point your site root to your wiki:

RewriteRule ^/*$ %{DOCUMENT_ROOT}/w/index.php [L]

Note that we do not recommend doing a HTTP redirect to your wiki path or main page directly. As redirecting to the main page directly will hard-code variable parts of your wiki's page setup into your server config. And redirecting to the wiki path will result in two redirects. Simply rewrite the root path to MediaWiki and it will take care of the 301 redirect to the main page itself.

If using VirtualHosts, place the rewrite rules into the virtual host declaration!


A common beginner's mistake is to install MediaWiki itself (the source code, not the short url) in /wiki instead of /w. Once installed they would realize the mistake when trying to configure Short URLs (which would become difficult as the virtual path then conflicts with the real path).

There is a manual for moving a wiki in general, however that is too complicated if all you need is to change the installation directory (and stay on the same server, same database and same hostname).

Here is what you have to do:

  • Backup LocalSettings.php and any other config files you may have created (such as your .htaccess).
  • Rename the installation directory of MediaWiki on your server from /wiki to /w.
  • Set $wgScriptPath in LocalSettings.php to "/w" and remove (or comment out) any definition of $wgArticlePath (this variable will be changed again when setting up Short URLs, further on)
  • At this point your wiki should be working normally at example.org/w
  • Now go through the regular guide to set up short URLs
  • Perform a few tests on your wiki to make sure nothing is broken. Edit a page, visit a few different pages, etc. If anything seems abnormal, revert the changes by restoring your backup of LocalSettings.php and other relevant files you might have changed during configuration of short URLs and rename your folder back to /wiki.

Note for shared hosting users: Many shared hosting plans offer an application manager to automatically Install, Update and Backup applications such as MediaWiki. If your plan has this and if you want to keep using these features, you should contact their tech support and let them know you just manually changed your MediaWiki installation directory.





  1. Bugzilla mod_rewrite for ampersand bug, partially resolved for some users, but only after 13 years