https://issues.apache.org/bugzilla/show_bug.cgi?id=57509
Mark Thomas changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=57509
Shelson Ferrari changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXE
https://issues.apache.org/bugzilla/show_bug.cgi?id=57509
--- Comment #6 from Konstantin Kolinko ---
Fixed in Tomcat 7 by r1657591, will be in 7.0.60 onwards.
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://issues.apache.org/bugzilla/show_bug.cgi?id=57509
Konstantin Kolinko changed:
What|Removed |Added
Resolution|WONTFIX |FIXED
--- Comment #5 from Kon
https://issues.apache.org/bugzilla/show_bug.cgi?id=57509
--- Comment #4 from Konstantin Kolinko ---
(In reply to yangkun from comment #3)
Your diagnosis is wrong. We are not talking about request here. It is response
(the status line of a HTTP response) that does not fit the buffer used by
statu
https://issues.apache.org/bugzilla/show_bug.cgi?id=57509
--- Comment #3 from yangkun ---
If check the maxHttpHeaderSize careful, the error may be subdivide the
following cases:
1. the request uri more than maxHttpHeaderSize, it should be a 414-request
url too long
2. the request entity mor
https://issues.apache.org/bugzilla/show_bug.cgi?id=57509
--- Comment #2 from Christopher Schultz ---
It might be nice to do bounds-checking (or not) and use an application
exception instead of AAOOBE. Getting an AAOOBE usually indicates to me that
there is a software flaw, not a data flaw.
--
Y
https://issues.apache.org/bugzilla/show_bug.cgi?id=57509
Remy Maucherat changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
