This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10328 - change Accept-Charset to should not
Summary: change Accept-Charset to should not
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: XHR (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-09 12:38 UTC by Anne
Modified: 2011-12-20 19:44 UTC (History)
2 users (show)

See Also:

Attachments

Description Anne 2010-08-09 12:38:04 UTC 
Currently the specification states that Accept-Charset should be set as appropriate by the user agent. However, Accept-Charset is a useless header that is on its way out. Opera already dropped it from requests and Mozilla is planning to.

Alternatively maybe the specification should not say anything about Accept-Charset and Accept-Encoding except that authors do not have control over them and that content-encodings used in transmission are automatically decoded by the user agent.
Comment 1 Anne 2010-08-11 11:31:19 UTC 
Proposal for CfC: Do not say anything about Accept-Charset and Accept-Encoding in the send() method section.
Comment 2 Anne 2010-08-26 12:13:10 UTC 
Changed the specification as suggested.