>
> accessing a file like this results in the access-log in:
>
> [30/Aug/2001:17:13:13 +0200] "GET
> /files/sid00017/AR_1000A-TSS_report-TSS.PDF HTTP/1.1" 200 32768
> "https://ida.festbrueder.ch/site/files.pl?siteid=17"; "Mozilla/4.0
> (compatible; MSIE 5.01; Windows
>
> [30/Aug/2001:17:13:14 +0200] "GET
> /files/sid00017/AR_1000A-TSS_report-TSS.PDF
> HTTP/1.1" 200 40960 "-" "Mozilla/4.0 (compatible; MSIE 5.01; Windows
> NT)"195.141.44.1 - -
>
> [30/Aug/2001:17:13:14 +0200] "GET
> /files/sid00017/AR_1000A-TSS_report-TSS.PDF HTTP/1.1" 206 397776 "-"
> "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT)"
>
> All three entries comes out of an access to one file ... *?*
> am i doing
> this right?
>
yes, that's right - this is how your browser plugin handles byterange
requests, usually by terminating the current request and initiating a new
one with the appropriate Range headers. last time I checked Netscape ended
up with 2 requests and MSIE with 3. that final request ought to be a 206,
though. add a PerlLogHandler that spits out $r->as_string (such as
Apache::DumpHeaders or Apache::DebugInfo) to see what is really going on.
fear not - Apache detects the closed connection and all writes to the wire
are changed into noops, meaning your handler will still run but not send any
data to the client. sounds strange, but the point of Range requests was to
reduce bandwith, not the processes of your server ;)
other than that, your code looks ok on first glance. what this the only
problem?
HTH
--Geoff
--Geoff
