Last modified: 2014-09-23 23:59:34 UTC
Created attachment 5312 [details] Fix "The Content-Location entity-header field MAY be used to supply the resource location for the entity enclosed in the message when that entity is accessible from a location separate from the requested resource's URI." http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.14
*Bulk BZ Change: +Patch to open bugs with patches attached that are missing the keyword*
Adding the "need-review" keyword for patches that need review by developers. Jakub, thank you for your patch, and sorry it's taken so long for a response on this!
Does anybody anywhere do anything with the content-location header?
Hi Jakub, thank you for the patch! As you may already know, MediaWiki is currently revamping its PHP-based parser into a "Parsoid" prototype component, to support the rich-text Visual Editor project: https://www.mediawiki.org/wiki/Parsoid https://www.mediawiki.org/wiki/Visual_editor Folks interested in enhancing the parser's capabilities are very much welcome to join the Parsoid project, and contribute patches as Git branches: https://www.mediawiki.org/wiki/Git/Tutorial#How_to_submit_a_patch Compared to .diff attachments in Bugzilla tickets, Git branches are much easier for us to review, refine and merge features together. Each change set has a distinct URL generated by the "git review" tool, which can be referenced in Bugzilla by pasting its gerrit.wikimedia.org URL as a comment. If you run into any issues with the patch process, please feel free to ask on irc.freenode.net #wikimedia-dev and the wikitext-l mailing list. Thank you!
Our #REDIRECT does seem to match the Content-Location meaning.
Is this like "canonical url" for pages that show content primary addressable from a different url? MediaWiki redirects don't use 302 or 301, but just show the content of the intended page with a small note under the title indicating the redirect.