Last modified: 2014-11-17 10:19:47 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 T75510, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 73510 - HTTPS port is incorrect


Summary:	HTTPS port is incorrect

Status:	NEW

Product:	MediaWiki-Vagrant
Classification:	Unclassified
Component:	General (Other open bugs)
Version:	unspecified
Hardware:	All All

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Nobody - You can work on this!

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-17 10:00 UTC by Seb35
Modified:	2014-11-17 10:19 UTC (History)
CC List:	3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Seb35 2014-11-17 10:00:16 UTC

Symptom: With a fresh MediaWiki-Vagrant with the https role, the resources (JS+CSS) are not loaded over HTTPS because the $wgServer variable is set to WebRequest::detectServer() in /vagrant/settings.d/wiki/CommonSettings.php (see bug 66399).

Explaination: The HTTPS is performed using nginx as a reverse proxy, and the function WebRequest::detectServer() assume in this case the HTTPS port is standard (443) instead of 4430 in MediaWiki-Vagrant ($wgServer = 'https://127.0.0.1').

Comment 1 Seb35 2014-11-17 10:16:07 UTC

It could be used the config variable $wgHttpsPort introduced in bug 65184: in WebRequest::detectServer(), in the case of HTTPS behind a reverse proxy, use $wgHttpsPort (default is obviously 443).

This solution should be double-checked since it would impact Wikimedia servers.

Wikimedia Bugzilla is closed!

Search

Personal tools

Navigation

Links