Last modified: 2014-05-23 23:11:59 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 T67184, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 65184 - wgSecureLogin does not play nicely with HTTPS on non-standard port
wgSecureLogin does not play nicely with HTTPS on non-standard port
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
User login and signup (Other open bugs)
1.24rc
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-11 11:54 UTC by Arthur Richards
Modified: 2014-05-23 23:11 UTC (History)
1 user (show)

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


Attachments

Description Arthur Richards 2014-05-11 11:54:19 UTC
If you have HTTPS configured to run on a non-standard port (eg 4430 rather than 443) and you have $wgSecureLogin enabled, clicking on the 'login' link does not work.

This is problematic particularly for the 'https' role in mediawiki-vagrant (https://gerrit.wikimedia.org/r/#/c/132702/) since with vagrant, you cannot forward ports < 1024.
Comment 1 Gerrit Notification Bot 2014-05-11 12:27:41 UTC
Change 132799 had a related patch set uploaded by Awjrichards:
Make HTTPS port configurable

https://gerrit.wikimedia.org/r/132799
Comment 2 Gerrit Notification Bot 2014-05-11 12:39:33 UTC
Change 132801 had a related patch set uploaded by Awjrichards:
Enable https-related mw configuration

https://gerrit.wikimedia.org/r/132801
Comment 3 Gerrit Notification Bot 2014-05-23 22:47:06 UTC
Change 132799 merged by jenkins-bot:
Make HTTPS port configurable

https://gerrit.wikimedia.org/r/132799

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


Navigation
Links