https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #14 from Christopher Schultz ch...@christopherschultz.net
2010-12-03 11:11:26 EST ---
Fixed in trunk. Will be included in Tomcat 7.0.6.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
---
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
Christopher Schultz ch...@christopherschultz.net changed:
What|Removed |Added
Status|NEW
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #13 from Christopher Schultz ch...@christopherschultz.net
2010-11-05 13:17:46 EDT ---
Created an attachment (id=26259)
-- (https://issues.apache.org/bugzilla/attachment.cgi?id=26259)
Patch to docs describing the previous patch
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #10 from Christopher Schultz ch...@christopherschultz.net
2010-11-03 20:22:40 EDT ---
Created an attachment (id=26252)
-- (https://issues.apache.org/bugzilla/attachment.cgi?id=26252)
Patch to provide request-entity parsing for
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #11 from Christopher Schultz ch...@christopherschultz.net
2010-11-03 20:24:25 EDT ---
I ought to provide a documentation patch as well. One will be forthcoming.
Also: should I bother to log a WARN (or other level) message when
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #12 from Mark Thomas ma...@apache.org 2010-11-03 20:41:15 EDT ---
No need for a log message. We don't do it elsewhere in similar circumstances.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #8 from Christopher Schultz ch...@christopherschultz.net
2010-09-21 10:56:59 EDT ---
Mark, I've just glanced-over RFC 2616 and I can't find any HTTP methods
(defined in section 9) that specifically prohibit a request body.
On
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #9 from Mark Thomas ma...@apache.org 2010-09-21 15:36:42 EDT ---
(In reply to comment #8)
Mark, I've just glanced-over RFC 2616 and I can't find any HTTP methods
(defined in section 9) that specifically prohibit a request
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #2 from Christopher Schultz ch...@christopherschultz.net
2010-09-20 16:40:52 EDT ---
I'll copy my comments from the duplicate bug #49964 just so they're more likely
to be read:
My proposal is this (and I'm prepared to write
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #3 from Mark Thomas ma...@apache.org 2010-09-20 16:45:51 EDT ---
How about parsePutBodyParams (since POST will always be parsed) with values
false (default) or true?
The logic for STRICT_SERVLET_COMPLIANCE in 7.0.x has been
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #4 from Christopher Schultz ch...@christopherschultz.net
2010-09-20 16:50:00 EDT ---
In one of the discussions on the tomcat-user list, the OP had complained that
he couldn't pass parameters using methods such as DELETE, etc. I
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #5 from Mark Thomas ma...@apache.org 2010-09-20 16:54:15 EDT ---
OK. A comma separated list of method names would make sense in that case.
Although methods that are not allowed to have bodies should not be permitted.
--
https://issues.apache.org/bugzilla/show_bug.cgi?id=48692
--- Comment #7 from Christopher Schultz ch...@christopherschultz.net
2010-09-20 18:15:54 EDT ---
Okay, I've got my patch working in TC 7, and I've renamed the configuration
setting to the less unwieldy parseBodyMethods.
--
Configure
13 matches
Mail list logo
