Last modified: 2014-02-12 23:38:10 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 T46573, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 44573 - [Interwiki] Links should use HTTP or HTTPS URL protocol relative to current page
[Interwiki] Links should use HTTP or HTTPS URL protocol relative to current page
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Interwiki (extension) (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: X!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-01 09:30 UTC by badon
Modified: 2014-02-12 23:38 UTC (History)
1 user (show)

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


Attachments

Description badon 2013-02-01 09:30:35 UTC
The Interwiki table currently requires the specification of the protocol. Instead, there should be an indication of whether the server at the destination supports HTTPS, and then the protocol should be selected dynamically, to match the protocol in use on the current page. If HTTPS is not indicated as being supported, then the Interwiki extension should fall back to HTTP by default.

I tested this on MediaWiki 1.18.x, using the older version of Interwiki required for 1.18. I looked at the code changes, and didn't see anything recent that indicated protocol-relative URLs were implemented in newer versions. If I've overlooked it, apologies.
Comment 1 badon 2013-02-01 09:43:16 UTC
Looking here:

https://www.mediawiki.org/wiki/Special:Interwiki

It appears the extension already supports protocol relative URLs via MediaWiki's native handling, beginning with 1.18. I should have tested that. Maybe the included table should be updated with protocol relative URls for the projects that support HTTPS? I'll leave this open for now, since I think at least that much can be done. I'll also update the documentation for the extension.

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


Navigation
Links