Re: cookie-radius / http-equiv="cookie"

• From: Amos Jeffries <squid3@treenet.co.nz>
• Date: Sun, 24 Oct 2021 21:32:23 +1300
• To: ietf-http-wg@w3.org
• Message-ID: <bdae5cc6-4f4f-d5c9-467f-13cbafb0b10c@treenet.co.nz>

On 13/10/21 8:38 pm, Rafal Pietrak wrote:
> Dear Everybody,
> 
> Some time ago I've drafted a proposal for cookie-radius
> (https://datatracker.ietf.org/doc/draft-pietrak-cookie-scope/). This was
> not received well, so I've decided not to press the matter.
> 
> But, since then I've learned, that there is a (currently depreciated)
> http-equiv.set-cookie <meta> tag attribute. Since this was implemented
> in most browsers, may be an improved definition of it's semantics could
> make it useful again.
> 

Please be aware that "http-equiv" META are expected to cause the Browser 
the same behaviour as if the key name (here "set-cookie") was a received 
HTTP header.

So your proposal needs to be made to change RFC 6265 as changes to the 
Set-Cookie and Cookie headers themselves.


Amos

Received on Sunday, 24 October 2021 08:39:01 UTC