On 03/03/2016 22:18, rails wrote:
> I have a weird behavior in my tomcat (7).
>
> An external app sends a bunch of DELETE requests with a body to my TomCat
> WebApp.
> The body is being neglected in the webapp (I dont know why the app sends
> it, the paramters the webapp needs are in the url).
> When the app sends about 20 request - a few are being ignored by the webApp.
>
> Looking at the Tomcat access logs I see the following strange thing.
> Right after the delete (line 2) The body of the delete is concatenated to
> the next request as a prefix(line 3).
You need to use something like Wireshark to confirm that the requests
being sent are spec compliant. If they are, you could have hit a Tomcat
bug and we'll need the simplest possible test case you can put put
together to demonstrate the issue.
Mark
>
> Then I get 505.
>
> Below - line 3 contains a prefix before POST /rest/dogs/tag HTTP/1.1" 405
> 1013.
>
>
> 172.31.13.77 - - [03/Mar/2016:14:08:43 +0000] "GET /rest/dogs/123
> HTTP/1.1" 200 4095
> 172.31.13.77 - - [03/Mar/2016:14:09:07 +0000] "DELETE /rest/dogs/123
> HTTP/1.1" 200 63
> 172.31.13.77 - - [03/Mar/2016:14:09:07 +0000] "{..HERE IS THE
> BODY(PayLoad) OF PREVIOUS DELETE.....}POST /rest/dogs/tag HTTP/1.1" 405 1013
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
