Welcome! Log In Create A New Profile

Advanced

Re: client keep alive support under HTTP/1.0

March 05, 2012 05:00PM
Hi Valentin,

I can repeat your results with static files - keepalives work with HTTP/1.0 in that scenario. However, for responses via FCGI, a connection close is consistently sent. I found a post on the russian forum (thank you Google translate) that implies that the content-length header needs to be set on the application side. I had assumed that nginx would calculate the length and add the header, but this does not appear to be the case.

http://forum.nginx.org/read.php?21,1301720319,older

Thanks,

Dean
Subject Author Posted

client keep alive support under HTTP/1.0

dbanks March 02, 2012 05:04PM

Re: client keep alive support under HTTP/1.0

Valentin V. Bartenev March 04, 2012 08:46AM

Re: client keep alive support under HTTP/1.0

dbanks March 04, 2012 10:55PM

Re: client keep alive support under HTTP/1.0

Valentin V. Bartenev March 05, 2012 03:36AM

Re: client keep alive support under HTTP/1.0

dbanks March 05, 2012 05:00PM

Re: client keep alive support under HTTP/1.0

dbanks March 06, 2012 12:25PM

Re: client keep alive support under HTTP/1.0

Valentin V. Bartenev March 06, 2012 05:40AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 95
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready