W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: HTTP response cacheability and query components

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 18 Oct 2013 09:17:30 +0200
Message-ID: <5260E08A.5020400@gmx.de>
To: Zhong Yu <zhong.j.yu@gmail.com>, Sufian Rhazi <srhazi@imvu.com>
CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2013-10-18 02:30, Zhong Yu wrote:
> On Fri, Oct 18, 2013 at 7:37 AM, Sufian Rhazi <srhazi@imvu.com> wrote:
>> Hello,
>> I was looking into some surprising behavior in Akami, where they ignored the
>> query component of the requested resource's URI. A request to
>> http://foo/bar?baz=2 resulted in a cached response to a previous request
>> from http://foo/bar?baz=1. This struck me as unexpected, since browsers tend
>> to cache responses with respect to the URI query component, and would break
>> applications that expect to be able to use queries for pagination,
>> filtering, etc...
>> I found that RFC 2616 defines "Request-URI" as the abs_path component of the
> RFC 2616 doesn't even allow any "/bar?baz=1" request. The spec and the
> practice are clearly out of sync. You should probably consult http bis
> for a more up to date description of http protocol.

See <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/11>. This has 
been of the somewhat official RFC 2616 errata list for something like a 

> ...

Best regards, Julian
Received on Friday, 18 October 2013 07:18:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:19 UTC