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 15494 - Should Content-Transfer-Encoding be forbidden?
Summary: Should Content-Transfer-Encoding be forbidden?
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: XHR (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL: http://dvcs.w3.org/hg/xhr/raw-file/ti...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-10 13:56 UTC by Julian Reschke
Modified: 2012-05-14 14:18 UTC (History)
5 users (show)

See Also:

Attachments

Description Julian Reschke 2012-01-10 13:56:43 UTC 
The list of "author request headers" mentions Content-Transfer-Encoding. This is confusing as there is no such header field in HTTP (there is one in email, though).
Comment 1 Anne 2012-01-10 14:01:32 UTC 
I think you are confusing author request headers with headers that cannot be set by authors. What is wrong with prohibiting Content-Transfer-Encoding?
Comment 2 Julian Reschke 2012-01-10 14:26:45 UTC 
(In reply to comment #1)
> I think you are confusing author request headers with headers that cannot be
> set by authors. What is wrong with prohibiting Content-Transfer-Encoding?

a) yes, sorry.

b) as I said: what's the point in forbidding it when it doesn't exist?
Comment 3 Anne 2012-01-10 14:32:43 UTC 
I don't know.
Comment 4 Boris Zbarsky 2012-01-10 17:05:36 UTC 
Julian is right: there is no such header, so prohibiting it makes no sense.  Why was that text added to the spec?  Did it actually mean to prohibit setting Content-Encoding or Transfer-Encoding (or maybe both?)
Comment 5 Anne 2012-01-10 17:09:20 UTC 
Not sure. The header has been there since the draft of June 2007.
Comment 6 Julian Reschke 2012-01-10 17:15:53 UTC 
(In reply to comment #5)
> Not sure. The header has been there since the draft of June 2007.

See also <http://lists.w3.org/Archives/Public/public-webapi/2008May/0189.html>.
Comment 7 Anne 2012-05-14 13:41:20 UTC 
Transfer-Encoding is forbidden. I think the idea must have been to forbid Content-Encoding.
Comment 8 Anne 2012-05-14 14:18:44 UTC 
I removed Content-Transfer-Encoding.

http://dvcs.w3.org/hg/xhr/rev/33501b9188cb


It was originally added in 1.68 of http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest/Overview.src.html by the way without a clear mailing list discussion associated with it.