Mailing List Archive

Issue 1322 in cherokee: Keep alive headers are not send
Status: New
Owner: ----

New issue 1322 by soc...@anonsphere.com: Keep alive headers are not send
http://code.google.com/p/cherokee/issues/detail?id=1322

What steps will reproduce the problem?
1. Activate keep alive
2. Surf your page
3. Read the header

What is the expected output? What do you see instead?

There should be a header like

Connection: Keep-Alive
Keep-Alive: timeout=30
Transfer-Encoding: chunked

But instead:

Date: Thu, 22 Dec 2011 04:29:57 GMT
Server: Cherokee
Etag: "4eea426a=10b62"
Last-Modified: Thu, 15 Dec 2011 18:54:34 GMT
Content-Type: image/jpeg
Content-Length: 68450
Expires: Thu, 31 Dec 2037 23:55:55 GMT
Cache-Control: max-age=315360000, public

200 OK

I know it worked a few month ago - see the post in
http://code.google.com/p/cherokee/issues/detail?id=763

I didn't use the keep alive function as there were problems with ssl, but
now it does not send the header. And btw. where is the option for the
timeout?

What version of the product are you using? On what operating system?

Debian 6.0.3
Cherokee Web Server 1.2.101


_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev
Re: Issue 1322 in cherokee: Keep alive headers are not send [ In reply to ]
Updates:
Status: Invalid
Labels: Type-Other Component-Docs

Comment #1 on issue 1322 by ste...@konink.de: Keep alive headers are not
send
http://code.google.com/p/cherokee/issues/detail?id=1322

HTTP 1.1 doesn't require to have keep alive headers sent.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.1.2

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev