Re: Byteranges with 206 partial content
Beth Frank (efrank@ncsa.uiuc.edu)
Tue, 14 Nov 1995 18:25:33 -0600 (CST)
> > An additional feature is to say "give me a range if the document
> > hasn't changed, but if it has, send me the entire document". Similar
> > to If-modified-since, but still quite different... What would you
> > call such a header?
>
> If-Modified-Since (for the current case)
> Unless (for the generic case)
>
> > I will re-vamp a new version of the byterange draft reflecting these
> > changes, and will submit it for review in http-wg shortly.
>
> I am willing to proceed with this in the main HTTP/1.1 spec, since the
> changes required are interwoven with the description of GET and caching.
>
> However, I am not willing to support multiple ranges within a single
> request at the current time, so no multipart/x-byteranges.
>
> ...Roy T. Fielding
> Department of Information & Computer Science (fielding@ics.uci.edu)
> University of California, Irvine, CA 92717-3425 fax:+1(714)824-4056
> http://www.ics.uci.edu/~fielding/
>
Could we use extra parameters in Request-Range as Shel Kaphan suggested instead
of having interactions between headers?