New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users

Issue metadata

Status: Fixed
Last visit > 30 days ago
Closed: Oct 2010
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

  • Only users with Commit permission may comment.

Sign in to add a comment

Issue 58459: Add X-Purpose header to prefetch requests

Reported by, Oct 8 2010 Project Member

Issue description

Right now prefetch requests from webkit contain no marker header at all.  This is inconsistent with Mozilla (which sends the admittedly awful X-Moz header) and Safari (which for preview fetches sends the header X-Purpose).

Since for preview Safari sends X-Purpose: preview in the request, and since for prefetch Firefox sends X-Moz: prefetch, I propose the best way to split the difference is to send X-Purpose: prefetch from Chrome.

There's been a lot of discussion in webkit about this, and some resistance there.  As a result, I think we should land something in Chrome to send this header for M8, and hopefully get WebKit on board for a future revision.

Comment 1 by, Oct 10 2010

Status: Fixed
This is landed in webkit, as  bug 46529 . , and Chrome has already gardenned past this revision.

The Link header changeset, at , includes a functional test that asserts this is working as  As well, the link header has to separately set this header, and it does, so when the link header lands this header will still work for all requests.

Comment 2 by, Oct 12 2012

Project Member
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

Comment 3 by, Mar 10 2013

Project Member
Labels: -Area-Internals -Internals-Network Cr-Internals Cr-Internals-Network

Sign in to add a comment