tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Deshayes" <ericdesha...@gmail.com>
Subject Re: Connection:close request returns a response without any content-length or Transfer-Encoding: chunked
Date Thu, 17 May 2007 00:28:26 GMT
Sorry, i forgot to mention I was working with JBoss 4.0.3 SP1, so I assume
Tomcat 5.5.9.

Here are some example to illustrate my case.
The first one i my problem.
Is that a fix bug? if so, In which version of TOmcat has it been fixed? It
seems to work in the latest tomcat 5.5 version (5.5.23)
If not, am I missing something from the Http specs?
Regards,
Eric


Example with Tomcat 5.5.9 (connection : close and NO content-length or
Transfer-Encoding provided):

GET / HTTP/1.1
Host: 127.0.0.1:18080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3)
Gecko/20070309 Firefox/2.0.0.3
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
,text/plain;q=0.8,image/png,*/*;q=0.5
Connection: close


HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1
date=200510231751)/Tomcat-5.5
Set-Cookie: JSESSIONID=7B90F594FCF9AB6A6AF690352724A94F; Path=/
Content-Type: text/html;charset=ISO-8859-1
Date: Thu, 17 May 2007 00:19:04 GMT
Connection: close

Second example with Tomcat 5.5.9 (connection : close and Transfer-Encoding
provided)
GET / HTTP/1.1
Host: 127.0.0.1:18080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3)
Gecko/20070309 Firefox/2.0.0.3
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
,text/plain;q=0.8,image/png,*/*;q=0.5

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1
date=200510231751)/Tomcat-5.5
Set-Cookie: JSESSIONID=8306B59382F5277A0782B98F9362213A; Path=/
Content-Type: text/html;charset=ISO-8859-1
Transfer-Encoding: chunked
Date: Thu, 17 May 2007 00:19:25 GMT


Finally, I have tried with the latest Tomcat version 5.5.23 (no connection :
close and content-length provided)

GET / HTTP/1.1
Host: 127.0.0.1:18080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3)
Gecko/20070309 Firefox/2.0.0.3
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
,text/plain;q=0.8,image/png,*/*;q=0.5

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 8132
Date: Thu, 17 May 2007 00:19:48 GMT

Another test with Tomcat 5.5.23 (connection : close and content-length
provided):
GET / HTTP/1.1
Host: 127.0.0.1:18080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3)
Gecko/20070309 Firefox/2.0.0.3
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
,text/plain;q=0.8,image/png,*/*;q=0.5
Connection: close

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 8132
Date: Thu, 17 May 2007 00:20:10 GMT
Connection: close









On 5/16/07, Eric Deshayes <ericdeshayes@gmail.com> wrote:
>
> Hi,
> is that normal that when the header of my request contains
> Connection:close, the response I get does not contain any  content-length or
> Transfer-Encoding header??
>
> When, the Connection: close header is not a header of the request, I get
> either a content-length or Transfer-Encoding header.
>
> Thanks for your help!!
> Eric
>
> --
> ----------------------------------------------------------------------
> ERIC DESHAYES
>
>


-- 
----------------------------------------------------------------------
ERIC DESHAYES

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message