Mailing List Archive: Apache: Bugs

[Bug 43882] - Multiple Transfer-Encodings in requests handled improperly

Index | Next | Previous | View Threaded

bugzilla at apache

Nov 16, 2007, 6:21 AM

Post #1 of 4 (287 views)
Permalink

[Bug 43882] - Multiple Transfer-Encodings in requests handled improperly

bugzilla at apache

Nov 16, 2007, 8:58 PM

Post #2 of 4 (269 views)
Permalink

[Bug 43882] - Multiple Transfer-Encodings in requests handled improperly [In reply to]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43882>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43882

------- Additional Comments From bjoern [at] hoehrmann 2007-11-16 20:58 -------
From the latest version:

/* RFC2616 allows qualifiers, so use strncasecmp */
if (!strncasecmp(tenc, "chunked", 7) && !ap_strchr_c(tenc, ',')) {
ctx->state = BODY_CHUNK;
}
else {
/* Something that isn't in HTTP, unless some future
* edition defines new transfer ecodings, is unsupported.
*/

I am a bit worried, I am unsure what "qualifiers" refers to and the code below
seems to match on "Transfer-Encoding: chunkedfoo" which it should not. And the
original example "Transfer-Encoding: gzip,chunked" is "in HTTP", Apache just
does not support it. So shouldn't this be something like

if (!strcasecmp(tenc, "chunked")) {
ctx->state = BODY_CHUNK;
}
else {
/* Other Transfer-Encodings are not implemented */

--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe [at] httpd
For additional commands, e-mail: bugs-help [at] httpd

bugzilla at apache

Nov 17, 2007, 12:29 AM

Post #3 of 4 (271 views)
Permalink

[Bug 43882] - Multiple Transfer-Encodings in requests handled improperly [In reply to]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43882>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43882

------- Additional Comments From nick [at] webthing 2007-11-17 00:29 -------
Björn, this is turning into discussion, and as such should be on dev [at] http, not
bugzilla. Do you follow that?

1. Qualifiers come from the BNF-style representation of the header, which means
something like
Transfer-Encoding: chunked;foo=bar
is syntactically valid. But in practice, no qualifiers are defined.

2. gzip is a content-encoding, not a transfer-encoding. The passage in RFC2616
that suggests otherwise is clearly a drafter who'd been staring at it too long,
and had a brainfart.

3. You're right about "chunkedfoo" - I'll fix it. If noone shouts, I'll just
set it back to strcasecmp, so we don't support any qualifiers. As it happens,
I'd already realised it wasn't right, but just wasn't rushing the job again:-)

Thank you for your attention to detail.

--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe [at] httpd
For additional commands, e-mail: bugs-help [at] httpd

bugzilla at apache

Nov 17, 2007, 1:24 AM

Post #4 of 4 (270 views)
Permalink

[Bug 43882] - Multiple Transfer-Encodings in requests handled improperly [In reply to]

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads