httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Kew <n...@webthing.com>
Subject Re: AP_CONN_CLOSE on force-response-1.0
Date Tue, 09 Oct 2007 14:13:00 GMT
On Tue, 9 Oct 2007 16:54:21 +0400
Aleksey Midenkov <asm@uezku.kemsu.ru> wrote:

> I believe the line making the connection always 'AP_CONN_CLOSE' on 
> force-response-1.0 is a erroneous leftover. The 1.0 should keep the
> connection alive if the browser will ask it to do so.
> 
> > httpd-trunk/modules/http$ grep -n -C 3 force-response-1.0
> > http_filters.c ...
> > 700:    /* kludge around broken browsers when indicated by
> > force-response-1.0 701-     */
> > 702-    if (r->proto_num == HTTP_VERSION(1,0)
> > 703:        && apr_table_get(r->subprocess_env,
> > "force-response-1.0")) { 704-        *protocol = "HTTP/1.0";
> > 705-        r->connection->keepalive = AP_CONN_CLOSE;
>               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > 706-    }
> > ...

Have you verified what happens if you remove that line?
Does it then respect exactly what the client asked for
if there's a Connection: header in the request?
And what does it then do if there isn't one?

-- 
Nick Kew

Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/

Mime
View raw message