DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21378>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21378 Transfer-Encoding: identity not supported + possible patch [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From [EMAIL PROTECTED] 2003-07-07 19:53 ------- Eric, please correct me if I am wrong, but it seems there's a certain terminology confusion. 'Identity' is a content encoding, not a transfer encoding. RFC 2616 defines only one valid transfer encoding: chunked. I think the fix suggested by Brent is indeed the right one. Transfer-encoding & Content-Length headers are mutually exclusive. We just have to print a BIIIIIIIIG FAT waring message in case transfer encoding is anything but chunked and return the input stream as is Am I missing something? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
