Last modified: 2014-09-23 23:59:34 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 T17560, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15560 - Redirected pages should send Content-Location header
Redirected pages should send Content-Location header
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.14.x
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/wiki/Vld
: patch, patch-need-review
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-11 11:02 UTC by Jakub Vrána
Modified: 2014-09-23 23:59 UTC (History)
6 users (show)

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


Attachments
Fix (614 bytes, patch)
2008-09-11 11:02 UTC, Jakub Vrána
Details

Description Jakub Vrána 2008-09-11 11:02:46 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
Comment 1 p858snake 2011-04-30 00:08:52 UTC
*Bulk BZ Change: +Patch to open bugs with patches attached that are missing the keyword*
Comment 2 Sumana Harihareswara 2011-11-09 19:25:38 UTC
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!
Comment 3 Bawolff (Brian Wolff) 2011-12-22 00:31:17 UTC
Does anybody anywhere do anything with the content-location header?
Comment 4 au 2012-06-17 18:40:59 UTC
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!
Comment 5 Platonides 2012-06-17 22:08:56 UTC
Our #REDIRECT does seem to match the Content-Location meaning.
Comment 6 Krinkle 2012-06-17 22:11:45 UTC
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.

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


Navigation
Links