Author: markt Date: Thu Nov 7 10:11:11 2013 New Revision: 1539584 URL: http://svn.apache.org/r1539584 Log: Clarify
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=1539584&r1=1539583&r2=1539584&view=diff ============================================================================== --- tomcat/tc6.0.x/trunk/STATUS.txt (original) +++ tomcat/tc6.0.x/trunk/STATUS.txt Thu Nov 7 10:11:11 2013 @@ -94,7 +94,7 @@ 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 + markt: RFC2616 states that multiple headers of the same name 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 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org