On Fri, 8 Jun 2001, Greg Stein wrote:
> Hah! Not even. I've been thinking about our filters quite a bit recently,
> and I was going to go and dig up this patch. *snicker*
I've got the apr-util end ready to commit... I'm just holding off until I
figure out what to do with Apache. Should be today sometime.
> > So in the code below, what would be the right thing to stick in the "XXX:
> > handle error" spot?
>
> Dunno. Some kind of magic error bucket? Recovering from errors during filter
> processing is totally undefined. If you've sent data to the client, then
> there isn't much that you *can* do except to:
>
> *) log an error
> *) close the connection ("unexpectedly" for the client)
There are special protocol rules for byteranges, though... You're
supposed to satisfy as many of the requested ranges as you can, IIRC...
only if NONE of them are satisfiable is it really an error. I think. Is
that right? I guess I have to go read the damned RFC. =-)
--Cliff
--------------------------------------------------------------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
