Mailing List Archive

> > The requested URL /pub/tex/;bytes=190- was not found on this server.<P>

On a hunch I just looked through telescope.org's transfer log:

somewhere.com - - [16/Oct/1995:21:04:26 +0100] "GET /gfx/login.gif;bytes=7- HTTP/1.0" 404 803
somewhere.com - - [16/Oct/1995:21:15:07 +0100] "GET /gfx/bar-name.gif;bytes=245- HTTP/1.0" 404 816

I'm getting lots and lots of these each day. Looks like some browser is
trying to use byte ranges (incorrectly) to get the end of partial
transfers; Ouch!

Mark
Mark J Cox, mark@telescope.org -- URL:http://www.telescope.org/mark.html
University of Bradford, England ---------- tel +44.1274.384070/fax 391333

> >
> > The browser in use was Netscape 2.0 on a NetBSD 1.0 kernel.
^^^^^^^^^^^^

QED.

I've seen 2.0 attempt to add all manner of garbage to the end of some
documents.

The usual giveaway is when it fails, and leaves an ugly "400 not found"
type message at the foot of the page and a URL with something like
";bytes=200" added to the end.

It puts our bugs into context :-)

rob

On Tue, 17 Oct 1995, Mark J Cox wrote:
> > > The requested URL /pub/tex/;bytes=190- was not found on this server.<P>
>
> On a hunch I just looked through telescope.org's transfer log:
>
> somewhere.com - - [16/Oct/1995:21:04:26 +0100] "GET /gfx/login.gif;bytes=7- HTTP/1.0" 404 803
> somewhere.com - - [16/Oct/1995:21:15:07 +0100] "GET /gfx/bar-name.gif;bytes=245- HTTP/1.0" 404 816
>
> I'm getting lots and lots of these each day. Looks like some browser is
> trying to use byte ranges (incorrectly) to get the end of partial
> transfers; Ouch!

Shit, I've gotten tons of them today.

I'm so angry I could scream. Seriously, I wish netscape would put a
*little* more thought into designing these things! The byterange
proposal is one I've argued against on http-wg, but who listens to me...

Brian

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com brian@hyperreal.com http://www.[hyperreal,organic].com/

> > > The requested URL /pub/tex/;bytes=190- was not found on this server.<P>
>
> On a hunch I just looked through telescope.org's transfer log:
>
> somewhere.com - - [16/Oct/1995:21:04:26 +0100] "GET /gfx/login.gif;bytes=7- HTTP/1.0" 404 803
> somewhere.com - - [16/Oct/1995:21:15:07 +0100] "GET /gfx/bar-name.gif;bytes=245- HTTP/1.0" 404 816
>
> I'm getting lots and lots of these each day. Looks like some browser is
> trying to use byte ranges (incorrectly) to get the end of partial
> transfers; Ouch!

And if you use ErrorDocument, there's a good chance that HTML
from another page is going to be embedded into the document you're
viewing... hence the original symptom of two documents glued together.

> Shit, I've gotten tons of them today.
>
> I'm so angry I could scream. Seriously, I wish netscape would put a
> *little* more thought into designing these things! The byterange
> proposal is one I've argued against on http-wg, but who listens to me...

...none of us, that's for sure.


;-)