|Re: [jetty-users] HTTP 400 status code returned after Jetty server upgraded from 9.0 to 9.2|
I did try to disable RestEasy, and use the jetty servlet to create an example servlet, still same error code. I didn't notice any mismatch in the dependency jars. But this error code only happened when I use Jetty 9.2, and Jetty 9.0 just worked fine. Another interesting finding is that two wget clients had different results:
GNU Wget 1.11.4 Red Hat modified
--2015-08-13 16:02:30-- http://remotehost:2013/example
Connecting to remotehost:2013... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://remotehost:2013/example/ [following]
--2015-08-13 16:02:30-- http://remotehost:2013/example/
Reusing existing connection to remotehost:2013.
HTTP request sent, awaiting response... 200 OK
Saving to: `index.html'
GNU Wget 1.16.3 built on darwin14.3.0.
--2015-08-13 17:11:15-- http://127.0.0.1:2013/example
Connecting to 127.0.0.1:2013... connected.
HTTP request sent, awaiting response... 400 Bad Request
2015-08-13 17:11:16 ERROR 400: Bad Request.
From: jetty-users-bounces@xxxxxxxxxxx <jetty-users-bounces@xxxxxxxxxxx> on behalf of Joakim Erdfelt <joakim@xxxxxxxxxxx>
Sent: Thursday, August 13, 2015 12:40 PM
To: JETTY user mailing list
Subject: Re: [jetty-users] HTTP 400 status code returned after Jetty server upgraded from 9.0 to 9.2
Also, what are the jars/classes you have in your project?
I'm wondering if there is a fundamental conflict somewhere (like a mismatch in org.eclipse.jetty.http classes for example)
On Thu, Aug 13, 2015 at 9:33 AM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
Back to the top