Re: RFC7234: Can a request body form part of a "cache key"?

------ Original Message ------
From: "Alex Rousskov" <>
To: "" <>
Cc: "Julian Reschke" <>; "Adrien de Croy" 
Sent: 28/07/2016 11:26:39 AM
Subject: Re: RFC7234: Can a request body form part of a "cache key"?

>On 07/27/2016 03:37 PM, Julian Reschke wrote:
>>  On 2016-07-27 22:56, Adrien de Croy wrote:
>>>  maybe need something like
>>>  Vary: Request-Body
>>  I'd say this is implied anyway.
>RFC 7231 appears to imply the opposite: It explicitly allows GET
>requests with bodies

"A payload within a GET request message has no defined semantics;
sending a payload body on a GET request might cause some existing
implementations to reject the request."

Same for HEAD.
Does anyone allow bodies on GET?  We block them I think.

I've also seen bodies on CONNECT...


>while not placing any request-body-related
>restrictions on their response cachability and sharing AFAICT.
>Similarly, there are instructions for caching POST responses that do 
>mention request body importance (and nearly implying its irrelevance by
>mentioning GET hits for POST-cached responses).

Received on Thursday, 28 July 2016 01:00:48 UTC