httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: Spinning httpds - One Solution
Date Fri, 21 Aug 1998 04:06:31 GMT
If a hard_timeout is in scope it longjmps back to the main loop and aborts
everything.  How is your code even getting invoked?

Not that setting aborted is a bad thing, I'd rather we figure out what's
really going on before we make that change though. 


On Thu, 20 Aug 1998, Rasmus Lerdorf wrote:

> > r->connection->aborted is only set by Apache after a a soft timeout.
> > Well, I'll ignore other situations.
> > 
> > If the client just closes a connection, r->connection->aborted won't get
> > set.  Well, that isn't true.  Since the same code gets called on a timeout
> > then r->connection->aborted will actually get set if you get a SIGPIPE if
> > you are in a soft timeout, but not if you are in a hard timeout even if
> > the timeout has nothing to do with the connection being aborted.
> > 
> > Why?  Haven't a clue, you would have to ask someone who has a clue.  But
> > you should listen to the return value from rwrite.
> Aha!  That answers a long outstanding headscratcher for me.  Is there a
> good reason for r->connection->aborted not getting set if a client closes
> the connection irregardless of the timeout state?  It would certainly make
> life easier on me in PHP land if this was the case.
> -Rasmus

View raw message