You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2013/07/26 10:08:34 UTC

[Bug 55310] New: Request body exposed as part of other request

https://issues.apache.org/bugzilla/show_bug.cgi?id=55310

            Bug ID: 55310
           Summary: Request body exposed as part of other request
           Product: Tomcat 7
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: Connectors
          Assignee: dev@tomcat.apache.org
          Reporter: abishek.bb@gmail.com

I am using Asynchronous servlet with Tomcat 7 and also jersey APIs in my 
application.

I see request body of one request forming a part of other request which happens
to be jersey API.
And in turn, the jersey API request becomes a bad request and returns 405.

This is blocker for my work as I could not use my application.

Please let me know if there needs to be a configuration change.

Or Please let me know if its a bug in tomcat.

I see similiar bugs reported which say request body exposed in some tomcat
versions.  Then I took latest version(7.0.42) where it is fixed.  But I see the
issue in that version.

Please let me know if you need more info.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 55310] Request body exposed as part of other request

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55310

Abishek <ab...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |abishek.bb@gmail.com
            Version|unspecified                 |7.0.42

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 55310] Request body exposed as part of other request

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55310

--- Comment #2 from Abishek <ab...@gmail.com> ---
(In reply to Mark Thomas from comment #1)
> In the significant majority of cases this turns out to be an application
> issue not a Tomcat one. Please debug this on the Tomcat users mailing list.
> 
> Feel free to re-open this issue if you reach either of the following points:
> 
> - you have a repeatable test case that demonstrates the issue
> 
> - you have identified a code path within Tomcat that could lead to request
> mix-up

Thanks Mark.

I will check my application.  I did not get any clue though.

Let me give you more info.
Request body of requests using asynchronous servlets are mixing up with jersey
API requests.

Should I close request using async servlets somewhere ? No clue whatsoever.
Please help me.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 55310] Request body exposed as part of other request

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55310

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
In the significant majority of cases this turns out to be an application issue
not a Tomcat one. Please debug this on the Tomcat users mailing list.

Feel free to re-open this issue if you reach either of the following points:

- you have a repeatable test case that demonstrates the issue

- you have identified a code path within Tomcat that could lead to request
mix-up

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org