Author: markt
Date: Tue Nov 19 09:58:40 2013
New Revision: 1543360
URL: http://svn.apache.org/r1543360
Log:
Formatting (line length)
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=1543360&r1=1543359&r2=1543360&view=diff
==============================================================================
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Tue Nov 19 09:58:40 2013
@@ -93,7 +93,12 @@ PATCHES PROPOSED TO BACKPORT:
* Better adherence to RFC2616 for content-length headers.
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.
+ +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 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
