Re: [jetty-users] HTTP 400 status code returned after Jetty server upgra

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

I agree with Lothar, at this point we need to see a tcpdump (the raw, on-network, as-sent) bytes to get an inkling on what's going on.

I trust curl and wget to do the right thing.

However, while they could be doing the right thing, something else is modifying that right thing before it gets to the server.

Such a modification should be obvious when analyzing a tcpdump.

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Fri, Aug 14, 2015 at 6:36 AM, Lothar Kimmeringer <job@xxxxxxxxxxxxxx> wrote:

Hi,

Am 13.08.2015 um 23:18 schrieb X Z:
> wget --version
> GNU Wget 1.11.4 Red Hat modified
[...]
> HTTP request sent, awaiting response... 200 OK
[...]
> wget --version
> GNU Wget 1.16.3 built on darwin14.3.0.
[...]
> 2015-08-13 17:11:16 ERROR 400: Bad Request.

Can you do a TCP-dump on the server-side with these two requests
and compare the two HTTP-request on byte-level?

The server dump doesn't look wrong IME.


Cheers, Lothar

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users