Re: Tomcat access log - body of a request shows in the next request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, On 3/4/16 3:26 AM, Mark Thomas wrote: > 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. Even if the messages are NOT spec-compliant, Tomcat shouldn't treat one request as two. (Unless the pipelined message is so mangled that the client really is making more than one request on a single connection .) - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlbZzIAACgkQ9CaO5/Lv0PAghQCcDabSaI6RdCwQuHETrpxICHWZ tWoAmwcl6EhwFHWzluEwHvYxRT1UX0yC =xVYr -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat access log - body of a request shows in the next request
In addition to Mark's answer:
Please add the *exact* tomcat version number ("7" is not sufficient)
that you're running (make sure it's not an old one - it's unnecessary to
hunt down bugs if they're long fixed.
Also, when you crosspost
(http://serverfault.com/questions/761445/tomcat-access-log-body-of-a-request-shows-in-the-next-request.
Elsewhere?), please mention this in all places, you're generating
duplicate work or dangling unanswered threads in one or more places.
More here:
http://meta.stackexchange.com/questions/141823/why-is-cross-posting-wrong-on-an-external-site
Olaf
Am 04.03.2016 um 09:26 schrieb Mark Thomas:
> 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 +] "GET /rest/dogs/123
>> HTTP/1.1" 200 4095
>> 172.31.13.77 - - [03/Mar/2016:14:09:07 +] "DELETE /rest/dogs/123
>> HTTP/1.1" 200 63
>> 172.31.13.77 - - [03/Mar/2016:14:09:07 +] "{..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
>
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat access log - body of a request shows in the next request
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 +] "GET /rest/dogs/123
> HTTP/1.1" 200 4095
> 172.31.13.77 - - [03/Mar/2016:14:09:07 +] "DELETE /rest/dogs/123
> HTTP/1.1" 200 63
> 172.31.13.77 - - [03/Mar/2016:14:09:07 +] "{..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
Tomcat access log - body of a request shows in the next request
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).
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 +] "GET /rest/dogs/123
HTTP/1.1" 200 4095
172.31.13.77 - - [03/Mar/2016:14:09:07 +] "DELETE /rest/dogs/123
HTTP/1.1" 200 63
172.31.13.77 - - [03/Mar/2016:14:09:07 +] "{..HERE IS THE
BODY(PayLoad) OF PREVIOUS DELETE.}POST /rest/dogs/tag HTTP/1.1" 405 1013
