Opened 11 years ago
Closed 10 years ago
#11555 closed enhancement (worksforme)
http/https aware Interwiki
| Reported by: | Dirk Stöcker | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Currently I can make an interwiki link only as http or https. I'd like to have these links http, when the pages are called with http and https when called with https, so that the user can choose.
Would be fine, when the interwiki link definition would support that (e.g. adding an variable support like ${urlmode} or whatever, which is then replaced by the current call-mode of the own webpage.
Should be relatively simple, but would ease the support of https.
Not that this must still be link specific, as some webpages don't support https.
Attachments (0)
Change History (6)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
I'm not so sure if // at the beginning really is supported as expected everywhere - It's rather uncommon and I'd like to avoid that. Also this style does not work in Trac elsewhere in the wiki pages f.e.
comment:3 by , 11 years ago
@dstoecker protocol-relative url format shown by @cboos is actually by far the most recommended way to approach this and should be used everywhere. If something doesn't work, it's a bug and should be patched.
comment:4 by , 11 years ago
Using the protocol-relative formats in InterMapTxt seems to work. Also, the protocol-relative syntax is already supported by some options (#11277) at least.
comment:5 by , 10 years ago
I don't see any open actions to take in this ticket given that // is supported. The ${urlmode} syntax may be preferred by the reporter, but we have 3 other developers making a case for the standard // syntax, and I can't see supporting multiple syntaxes for the same feature. Shall we close the ticket, or is there something to be done that I'm not seeing?
comment:6 by , 10 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
I've also seen Protocol-relative URLs like //example.com/ (apparently also known as network-path reference or scheme-relative URL) recommended as the solution to this problem.
Even if there are any issues (e.g. with old IE?) I would prefer any workarounds to be based on this standard syntax if possible.
Have you tried with InterMapTxt targets specified as
//example.com/URLs? That should be pretty close to what you're trying to achieve.