Last modified: 2014-06-13 10:58:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T68481, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66481 - Installer hardcodes a protocol to $wgServer
Installer hardcodes a protocol to $wgServer
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.22.7
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-11 15:19 UTC by [[kgh]]
Modified: 2014-06-13 10:58 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description [[kgh]] 2014-06-11 15:19:21 UTC
When installing a wiki the installer always hardcodes the protocol to $wgServer e.g.

$wgServer = "http://www.example.org";

Since MW 1.18+ allows for protocol relative settings to $wgServer the installer should probably always better add

$wgServer = "//www.example.org";

for the default install. Probably this bug is building on bug 44260. This setting tends to be painful if it is hardcoded with an explicit protocol so ...
Comment 1 [[kgh]] 2014-06-13 10:58:41 UTC
Hmm ..., I played a bit with this parameter. It turns out that it is useless if

$wgServer = "//www.example.org";

is set and either http or https is not configured for the URL. So if one only configured http one will imperatively have to set

$wgServer = "http://www.example.org";

or in the case of https

$wgServer = "https://www.example.org";

Only if both http and https is configured it makes sense to set this parameter to be protocol relative and additionally set $wgCanonicalServer to either on of them.

I guess I have no case here. Thus closing this as RESOLVED WONTFIX.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links