httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexei Kosut <ako...@leland.Stanford.EDU>
Subject Re: [PATCH] Re: mod_cern_meta/1500: mod_cern_meta corrupts memory pool (fwd)
Date Mon, 08 Dec 1997 23:25:43 GMT
On Mon, 8 Dec 1997, Dean Gaudet wrote:

> - Find out why the heck the auth crud is stored in r->connection.
>   Double check that it's properly reset after each during a keepalive
>   session.

Because way back when, around the time of Apache 0.8, when persistent
connections were first being talked about, the theory was that
authentication (and possibly other headers) would be sticky, that it would
roll over from one request to another, without needing to be
reauthenticated. Looking ahead to the future, the auth information was put
into r->connection, presuming that that would be a good place for it in
the future (but remember that at the time, there was only one request per
connection).

When the keep-alive protocol, and later HTTP/1.1, was finally written, the
idea of sticky headers was dropped (although I think there may be an I-D
on it still out there). When I implemented keep-alive in Apache 1.1, I
didn't want to deal with changing all the authentication stuff to move it
from the connection structure to the request one (originally, the
keep-alive stuff was just a loop in standalone_main() and a few lines in
send_http_header(). It got a lot more complicated later, but at first it
was very simple), so I just NULLed them in between each request. It seemed
easier.

-- Alexei Kosut <akosut@stanford.edu> <http://www.stanford.edu/~akosut/>
   Stanford University, Class of 2001 * Apache <http://www.apache.org> *



Mime
View raw message