| Re: [jetty-users] HTTP 400 status code returned after Jetty server upgraded from 9.0 to 9.2 |
|
Here is the details of http post request:
* Hostname was NOT found in DNS cache * Trying 127.0.0.1... * Connected to 127.0.0.1 (127.0.0.1) port 2013 (#0) > POST /mock/127.0.0.1 HTTP/1.1 > User-Agent: curl/7.37.1 > Host: 127.0.0.1:2013 > Accept: */* > Content-Type: application/json > Content-Length: 248 > * upload completely sent off: 248 out of 248 bytes < HTTP/1.1 400 Bad Request < Content-Length: 0 < Connection: close * Server Jetty(9.2.13.v20150730) is not blacklisted < Server: Jetty(9.2.13.v20150730) < * Closing connection 0 Here is the details of http get request:
* Hostname was NOT found in DNS cache * Trying 127.0.0.1... * Connected to 127.0.0.1 (127.0.0.1) port 2013 (#0) > GET /available HTTP/1.1 > User-Agent: curl/7.37.1 > Host: 127.0.0.1:2013 > Accept: */* > < HTTP/1.1 400 Bad Request < Content-Length: 0 < Connection: close * Server Jetty(9.2.13.v20150730) is not blacklisted < Server: Jetty(9.2.13.v20150730) < * Closing connection 0 Thanks zhong
From: jetty-users-bounces@xxxxxxxxxxx <jetty-users-bounces@xxxxxxxxxxx> on behalf of Joakim Erdfelt <joakim@xxxxxxxxxxx>
Sent: Wednesday, August 12, 2015 5:33 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 Just mocked this up based on your descriptions.
A Jetty server using Jetty 9.2.13.v20150730
A servlet on "/mock/*" that has a doGet() and doPost() enabled.
Had the implementation of this servlet just respond what it got.
Using curl to access said servlet. $ curl -vv http://127.0.0.1:2013/mock/127.0.0.1
* About to connect() to 127.0.0.1 port 2013 (#0)
* Trying 127.0.0.1...
* Adding handle: conn: 0x11588d0
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x11588d0) send_pipe: 1, recv_pipe: 0
* Connected to 127.0.0.1 (127.0.0.1) port 2013 (#0)
> GET /mock/127.0.0.1 HTTP/1.1
> User-Agent: curl/7.32.0
> Host: 127.0.0.1:2013
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 12 Aug 2015 21:32:07 GMT
< Content-Type: text/plain; charset=ISO-8859-1
< Content-Length: 62
* Server Jetty(9.2.13.v20150730) is not blacklisted
< Server: Jetty(9.2.13.v20150730)
<
GET Request received for http://127.0.0.1:2013/mock/127.0.0.1
* Connection #0 to host 127.0.0.1 left intact
$
$ curl -vv -H "Content-Type: application/json" --data @si.json
http://127.0.0.1:2013/mock/127.0.0.1
* About to connect() to 127.0.0.1 port 2013 (#0)
* Trying 127.0.0.1...
* Adding handle: conn: 0x12da920
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x12da920) send_pipe: 1, recv_pipe: 0
* Connected to 127.0.0.1 (127.0.0.1) port 2013 (#0)
> POST /mock/127.0.0.1 HTTP/1.1
> User-Agent: curl/7.32.0
> Host: 127.0.0.1:2013
> Accept: */*
> Content-Type: application/json
> Content-Length: 1103791
> Expect: 100-continue
>
< HTTP/1.1 200 OK
< Date: Wed, 12 Aug 2015 21:32:53 GMT
< Content-Type: text/plain; charset=ISO-8859-1
< Content-Length: 63
< Connection: close
* Server Jetty(9.2.z-SNAPSHOT) is not blacklisted
< Server: Jetty(9.2.z-SNAPSHOT)
<
POST Request received for http://127.0.0.1:2013/mock/127.0.0.1
* Closing connection 0
Can you use "-vv" on your curl line too?
Joakim Erdfelt /
joakim@xxxxxxxxxxx
On Wed, Aug 12, 2015 at 2:06 PM, X Z <bohr@xxxxxxxx> wrote:
|