- From: Jonathan A Rees <rees@mumble.net>
- Date: Tue, 27 Mar 2012 09:47:34 -0400
- To: James Leigh <james@3roundstones.com>
- Cc: public-lod community <public-lod@w3.org>
Well foo, I can't find it in the errata list, I take that back. But it is fixed in HTTPbis. http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-19#section-7.3.4 Jonathan On Tue, Mar 27, 2012 at 9:44 AM, Jonathan A Rees <rees@mumble.net> wrote: > On Mon, Mar 26, 2012 at 9:15 PM, James Leigh <james@3roundstones.com> wrote: >> Could this 308 (Permanent Redirect) give us a way to cache a probe URI's >> definition document location? >> >> An issue people have with httpRange-14 is that 303 redirects can't be >> cached. If we could agree to use a 308 response as a cache-able >> alternative to 303, we could reduce server load and speed client URI >> processing (by caching the result of a probe URI). >> >> Thoughts? >> James > > The HTTP bug where 303 response to a GET is uncachable has been a > known mistake for a long time; it's been in the RFC 2616 errata list, > and has been fixed in most drafts of HTTPbis. > > Clients should have seen the errata and fixed this eons ago. > > Jonathan
Received on Tuesday, 27 March 2012 13:48:08 UTC