I just tested my keep-alive via telnet as you suggested.
I am using embperl and mod_perl.
I was able to make three separate requests on the same connection
without a problem.
Here is a copy of one of the headers:
HTTP/1.1 200 OK
Date: Fri, 31 Mar 2000 23:59:53 GMT
Server: Apache/1.3.9 (Unix) mod_perl/1.21 mod_ssl/2.4.8 OpenSSL/0.9.4
Set-Cookie: GWCUID=ad912cb7a7e771d1; domain=.genwax.com; path=/; expires=Friday,
31-Dec-2010 14:00:00 GMT
Content-Length: 26413
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
does yours come back with:
200 OK
Connection: Keep-Alive
Keep-Alive: timeout etc.. ??
cliff rayman
genwax.com
Jaime Teng wrote:
> >Keep-Alive is a function of the web-server. There are no script changes
> >involved to keep a connection alive. All you have to do on the server side
> >is to enable Keep-Alive. See http://www.apache.org/docs/keepalive.html for
> >an explanation.
>
> The web servers (apache, IIS) already have the Keepalive setting on and
> properly keeps connection alive. The web server keeps the connection alive
> when the browser is fetching static HTML pages.
>
> Proof: telnet to fetch static document will remain open, ie, i can
> fetch as many static pages from one single telnet session without
> getting "connection to host lost" so long I specify
> "Connection: Keep-Alive" in the telnet session.
>
> BUT the connection dies when the browser is fetching dynamic mod_perl pages.
> This is where I would like to know if this is a perl/modperl issue or an
> apache/IIS issue.
>
> Proof: telnet to fetch the perl script will be closed after perl
> finished running the script, ie, I get "connection to host lost"
> immediately after the script finishes.
>
> is this a perl/modperl issue? where can i get docs to solve this?
>
> jaime
