Bug 13377 - Expose Accept* HTTP headers via SPI to applications
Summary: Expose Accept* HTTP headers via SPI to applications
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 523.x (Safari 3)
Hardware: Macintosh OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-17 15:45 PDT by Nicholas Shanks
Modified: 2007-04-17 16:59 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicholas Shanks 2007-04-17 15:45:50 PDT
It would be useful for users to be able to modify the Accept, Accept-Language, Accept-Charset, Accept-Encoding and Accept-Ranges HTTP headers. For instance Alexey has had trouble with some servers choking on languages with q-values, and wanted them removed, whilst I would like to specify my own values for (British) English, French and German, and do not come across servers that this causes a problem on. I also don't want to use 1.0, 0.66 and 0.33 which is what Firefox would assign the three languages if I put them in that order, but perhaps 1.0, 0.4, 0.1 !
Note also that most browsers (Opera being the primary exception) send a different set of MIME types in the Accept header depending on how the resource request was generated (e.g. the main resource might want to accept */*, whilst you'd be more choosy from an image, script or link element). See bug 3510 for more on this.

Since there is no "one size fits all" solution to this, I suggest that the headers are exposed via an API allowing UAs such as Safari to provide an interface by which the user can set their own values for these headers. Obviously this would be an advanced feature and suitable defaults still need to be decided upon, but it would create the opportunity for users to configure their systems for their own environment.
Comment 1 Nicholas Shanks 2007-04-17 15:47:41 PDT
Sorry, that reference for more info on what browsers send what headers should have referred to bug 12296.