[
https://jira.jboss.org/jira/browse/JBWEB-117?page=com.atlassian.jira.plug...
]
Mike Millson updated JBWEB-117:
-------------------------------
Attachment: before-patch.cap.tar.gz
Packet capture showing the issue. Packet 25 shows AJP13 protocol sending "400 Bad
Request".
ajp connector doesn't read post data and next request throw an
exception.
-------------------------------------------------------------------------
Key: JBWEB-117
URL:
https://jira.jboss.org/jira/browse/JBWEB-117
Project: JBoss Web
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: use mod_proxy_ajp or mod_jk and BASIC authentication.
Reporter: Jean-Frederic Clere
Assignee: Jean-Frederic Clere
Attachments: 512a.post, before-patch.cap.tar.gz
AJP sends 2 AJP messages together:
1 - request headers
2 - posted data
If an exception or error (like 401) occurs before read the posted data that data will be
handled like a request headers if it size is between 512 and 767.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira