httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexei Kosut <ako...@organic.com>
Subject Re: [PATCH] ETags and Last-Modified, take 3
Date Fri, 29 Aug 1997 21:09:24 GMT
On Fri, 29 Aug 1997, Rodent of Unusual Size wrote:

(on an unrelated note: I'll likely be unable to access my email from now
until sometime sunday. So if I seem somewhat quiet, that's why...)

>     Last-Modified and ETag headers generated by scripts are now taken
>     into consideration - which means that script output is now subject
>     to the HTTP/1.1 conditional header fields.

Haven't looked at the code, but +1 on the concept at least.

>     One thing I'm not sure about is how to handle a script that
>     sent headers that *didn't* meet the conditions.  At the moment
>     I'm treating it the same way as one which generated bogus headers
>     (i.e., slurp up all the output and return the error), but I could
>     see a long-running script turning this into a time-sink.  Should
>     maybe the script be killed?  Except I can see potential negative
>     side-effects from that, too..  Perhaps the kill_timeout() should be
>     moved to *after* the slurp..?

I don't think the script should be killed (some CGI scripts will do
important things during/after sending an entity). Maybe send it a SIGURG or
some other non-terminal signal, to tell it "hey, stop it, I'm not sending
anything anymore"?

>     And since Roy didn't like the unidiff last time, this one's a
>     context diff.  <g>

Hmm. I think it would look better as a unidiff :)

-- Alexei Kosut <akosut@organic.com>


Mime
View raw message