Test shows:
<link rel="EditURI" type="application/rsd+xml" href="https://secure.wikimedia.org/wikipedia/test/w/api.php?action=rsd" />
Version: unspecified
Severity: normal
Description
Description
Details
Details
- Reference
- bz29976
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T21270 Relative URIs in interwiki links table break interwiki transclusion | |||
| Resolved | None | T20664 Relative URIs in interwiki links table causes failed redirects | |||
| Resolved | None | T22342 Support for protocol-relative URLs | |||
| Resolved | Catrope | T31976 protocol relative uri for meta edituri |
Event Timeline
Comment Actions
Bryan.TongMinh wrote:
Putting this in the API component, even though this is in the HTML output of index.php, as it refers to an API module.
Comment Actions
I'd say if this needs to be changed, just use a local relative link with the path only. It'll be just as accurate, smaller in output, and slightly more likely to be supported by clients doing discovery.
Comment Actions
Created attachment 8808
dze path is simple
Relates to Bug 25648.
Fear is that some of the clients actually using this URL might not support any relative url form.
We probably need a set of testcases so that we can file upstream bugs.
Attached:
Comment Actions
(In reply to comment #4)
We could force it to always refer to HTTP.
With my pending wfExpandUrl() rewrite, we'd be able to do that, yes, with something like wfExpandUrl( $url, PROT_HTTP );
Comment Actions
(In reply to comment #5)
(In reply to comment #4)
We could force it to always refer to HTTP.
With my pending wfExpandUrl() rewrite, we'd be able to do that, yes, with
something like wfExpandUrl( $url, PROT_HTTP );
wfExpandUrl() rewrite done in r93258, will finish this soonish.