You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by ma...@apache.org on 2013/11/07 11:10:34 UTC
svn commit: r1539583 - /tomcat/tc6.0.x/trunk/STATUS.txt
Author: markt
Date: Thu Nov 7 10:10:34 2013
New Revision: 1539583
URL: http://svn.apache.org/r1539583
Log:
Add a response
Modified:
tomcat/tc6.0.x/trunk/STATUS.txt
Modified: tomcat/tc6.0.x/trunk/STATUS.txt
URL: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=1539583&r1=1539582&r2=1539583&view=diff
==============================================================================
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Thu Nov 7 10:10:34 2013
@@ -94,6 +94,11 @@ PATCHES PROPOSED TO BACKPORT:
http://people.apache.org/~markt/patches/2013-09-11-tc6-content-length.patch
+1: markt
+0: schultz: I don't see anywhere in RFC2616 that suggests that multiple Content-Length headers yields an invalid request. Another option for response code in this case might be 411 Length Required. There are some conditions under which Content-Type "RFC MUST" be ignored, and I don't see those cases in any of the *Processor classes.
+ markt: RFC2616 states that multiple headers of the same value may be
+ merged in to a single, multi-valued header without any change in
+ meaning. Content-Length is clearly defined as a single value
+ header. If multiple values are not permitted then neither are
+ multiple headers.
-1:
* Add support for limiting the size of chunk extensions when using chunked
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org