Glenn Strauss <[EMAIL PROTECTED]> writes: [...]
> I'm not sure the answer to this one: > Are protocol filters attached to the request (I think so) > or to the connection? If attached to the request, then > wouldn't they need to push-back excess data before the request > finishes if the data is to be used by later requests on the > same connection? > > The HTTP_IN filter allocates its ctx from r->pool, so it won't > survive multiple requests on the same connection. I don't think HTTP_IN would normally read more than one request at a time, but if it did, it could add an ephemeral connection filter and put the excess brigade in there. -- Joe Schaefer
