|General Settings: $wgServer|
|The base URL of the server.
|Introduced in version:||pre 1.1.0|
|Removed in version:||still in use|
|Allowed values:||URL prefix (protocol, host, optionally with port; no path portion)|
|Default value:||dynamically created|
|Other settings: Alphabetical | By function|
The base URL of the server, including protocol and without the trailing slash (eg,
http://www.mediawiki.org). Since 1.18 MediaWiki also supports setting $wgServer to a protocol-relative URL (e.g.,
//www.mediawiki.org). This is used for supporting both HTTP and HTTPS with the same caches by using links that work under both protocols. When doing this,
$wgCanonicalServer can be used to set the full URL including protocol that will be used in locations such as emails that don't support protocol relative URLs.
http://localhostand not to
//localhost! If it is, a number of things will break, e.g. links inside your wiki will not work, stylesheets will not display properly and many more. Set it to the actual base URL instead!
This is used when producing fully-qualified URLs pointing to the wiki, for instance:
- HTTP redirects on edit and to canonical URL spellings
- print footer
- links to articles from RSS/Atom feeds
- and more!
If the URL starts with https://, MediaWiki will assume that your wiki prefers the HTTPS protocol or supports it exclusively.
When $wgServer is not set, the default value is calculated automatically. Some web servers end up returning silly defaults or internal names which aren't what you want; for instance the ServerName directive in Apache's
httpd.conf may not be set or detected properly by the system, leaving you with an unexpected
http://localhost. It's always good to configure the web server properly. But you anyway are always strongly recommended to set $wgServer explicitly in your LocalSettings.php as there are other bugs that may arise from allowing it to be auto-detected, such as pollution of the MediaWiki cache.
In situations where a server URL is subject to change (ie: frequent Mediawiki installation porting, intranet access, etc.), setting $wgServer to
./ seems to work without causing the missing CSS issue. (Tested in Apache running on Windows.)