httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding" <>
Subject Re: [PATCH] ETags and Last-Modified, take 3
Date Thu, 04 Sep 1997 08:46:32 GMT
>I'll repeat again ... the server does kill CGIs.  They are killed as soon
>as the pool is cleared, whether that be because it was a HEAD and the
>headers have been read and sent to the client, or because it's anything
>else and a timeout occurs.  It is not trivial to "fix" this.  I don't even
>think it needs "fixing".  I don't understand people's reluctance to kill
>CGIs.  They are sent SIGTERM as soon as their pool is cleared, and SIGKILL
>if they haven't died within three seconds.  It's always been this way. 

Yes, I know, and it has always been wrong.  If the CGI script closes the
output and then does some cleanup, it can be killed during the cleanup
and the server has screwed things for no good reason.  It is utterly
nuts for the server to assume the CGI is broken just because the process
is still active after it sends the response.  If the CGI is broken,
it should twist on the vine until the webmaster notices that it is broken
and fixes the bloody thing.  Otherwise, the server will appear to randomly
corrupt databases and similar gateways when the load is high.

>> Also, an Etag must include a control stamp which is guaranteed to change
>> when any part of the content of the response would change.  That is
>> definitely not the case for the suggested change to mod_include.c, so
>> you'll have to remove that.
>I think I missed this ... what change to mod_include? 

The last part included the addition of set_etag in mod_include if the
xbithack is on, which is bad.


View raw message