>At 05:05 PM 9/2/95 -0400, Roy Fielding wrote: >>For obvious reasons, any browser that doesn't include all the ranges >>that it wants to accept is broken, unless it wants a 406 response instead. > >I think the term "range" is used incorrectly here. The only options are >either, "this very specific type" or "any specific type I haven't mentioned." Media ranges are defined in the spec. */*, text/*, and text/html are all media ranges in that they encomapass a range of actual media types. There are two ways to do content negotiation: preemptive or reactive. I think preemptive content negotiation is doomed to failure in the long term, which is why I added the 300 response code. When the day comes that preemptive content negotiation (Accept* headers) are more costly than reactive (an extra round-trip carrying a URC), then browsers and server can switch without changing the protocol. ....Roy T. Fielding Department of ICS, University of California, Irvine USA Visiting Scholar, MIT/LCS + World-Wide Web Consortium (fielding@w3.org) (fielding@ics.uci.edu)Received on Wednesday, 6 September 1995 11:48:12 EDT
This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:31:31 EDT