[jboss-jira] [JBoss JIRA] Commented: (JBWEB-117) ajp connector doesn't read post data and next request throw an exception.

Remy Maucherat (JIRA) jira-events at lists.jboss.org
Wed Sep 3 07:51:38 EDT 2008


    [ https://jira.jboss.org/jira/browse/JBWEB-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12427957#action_12427957 ] 

Remy Maucherat commented on JBWEB-117:
--------------------------------------

I think there are only two options:
- the scenario where mod_jk will send the body right away is well defined and can be detected, and it could be possible to code it in (it is a significant change though)
- remove this optimization from mod_jk and mod_proxy

> 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
>
> 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

        



More information about the jboss-jira mailing list