Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Connection : close request header and missing "Content-Length" in response

Hi Marcel,

There were some changes in recent jetty-7 releases to better handle closing with intermediaries. So please
try jetty-7.4.2 as it may well make this problem go away.

If not, please post again with a tcpdump/wireshark trace if possible.

thanks

On 24 June 2011 12:36, Marcel Casado <marcel@xxxxxxxx> wrote:
Hi,

I'm running CXF jax-ws web services with Jetty. I'm running a gateway that adds "Connection: close" headers to the request. The response that gets back includes a "Connection: close" header but does not contain a ""Content-Length" header and the response is not chuncked.

POST /wcs HTTP/1.1
X-CorrelationID: 7c49e6304e033fcc49f90000 1
Connection: close
Content-Length: 295
User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5
OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
Accept: */*
Via: 1.0 shockthemonkey.nextgen.mdl.nws.noaa.gov
<http://shockthemonkey.nextgen.mdl.nws.noaa.gov>  ()
Host: 192.168.43.20:8280<http://192.168.43.20:8280>
Content-Type: application/x-www-form-urlencoded

<?xml version="1.0" encoding="UTF-8"?><soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:ns="http://www.opengis.net/wcs/1.1"
xmlns:ns1="http://www.opengis.net/ows/1.1">  <soap:Header/>  <soap:Body>
<ns:GetCapabilities service="WCS" />  </soap:Body></soap:Envelope>

HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=ISO-8859-1
Connection: close
Server: Jetty(7.2.2.v20101205)

<soap:Envelope xmlns:soap="http


The same request using curl without adding the header just works fine:

POST /wcs HTTP/1.1
User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5
OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
Host: 192.168.43.20:8280<http://192.168.43.20:8280>
Accept: */*Content-Length: 295
Content-Type: application/x-www-form-urlencoded

<?xml version="1.0" encoding="UTF-8"?><soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:ns="http://www.opengis.net/wcs/1.1"
xmlns:ns1="http://www.opengis.net/ows/1.1">  <soap:Header/>  <soap:Body>
<ns:GetCapabilities service="WCS" />  </soap:Body></soap:Envelope>
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=ISO-8859-1
Transfer-Encoding: chunked
Server: Jetty(7.2.2.v20101205)

8000
<soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body><ns10:Capabilities
xmlns:ns23="http://www.w3.org/2001/SMIL20/Language"
xmlns:ns22="http://docs.oasis-open.org/wsrf/r-2"
xmlns:ns21="http://www.wcs.opengis.net/wsdl"
xmlns:ns20="http://www.java/lang"
xmlns:ns19="http://www.isotc211.org/2005/gts"
xmlns:ns18="http://www.opengis.net/gml/3.2"
xmlns:ns17="http://www.isotc211.org/2005/srv"
xmlns:ns16="http://www.isotc211.org/2005/gmd"
xmlns:ns15="http://www.isotc211.org/2005/gmx" xmlns:ns14="http


Adding the "Connection: close" header  to the curl request it makes it hang for ever.

Is this a bug in Jetty  ?

Thanks,

-Marcel


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users


Back to the top