W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1995

Re: draft-luotonen-http-url-byterange-00.txt

From: Ari Luotonen <luotonen@netscape.com>
Date: Wed, 27 Sep 1995 14:05:34 -0700 (PDT)
Message-Id: <199509272105.OAA11412@neon.netscape.com>
To: Mark Brown <mbrown@openmarket.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com

> * "separated by a colon" should read "separated by a semicolon"

Yes, will be fixed in the next revision of the draft.

> * The draft is silent on how the server should respond to a
>    very large integer parameter, e.g.
> 		http://host/dir/foo;bytes=-123456789012345678901234567890
>    This might be treated as a syntax error or might be treated as the
>    largest integer that the server can represent.

Any large number should be treated as the biggest possible value it
can have.  That is, the size of the document, size - 1, or whatever.
In the above case, it would be the size of the doc.  Will change to
spec to be more clear about it.

> * The draft says that large second numbers should be treated as referring
>    to the end of the document.  The draft also says that the first
>    number must always be less than or equal to the second number.
>    Suppose that dir/foo is a 1-byte file and the request is
>                 http://host/dir/foo;bytes=9-10
>    Using the first rule the server transforms the request into
>                 http://host/dir/foo;bytes=9-0
>    Is this now an error according to the second rule?  Or should
>    the server give some arbitrary response, e.g. return the last
>    byte of the file?

Should be treated a zero-length range.

Ari Luotonen				ari@netscape.com
Netscape Communications Corp.		http://home.netscape.com/people/ari/
501 East Middlefield Road
Mountain View, CA 94043, USA		Netscape Server Development Team
Received on Wednesday, 27 September 1995 14:11:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:15 UTC