W3C home > Mailing lists > Public > public-webappsec@w3.org > July 2015

Re: UPGRADE: 'HTTPS' header causing compatibility issues.

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 7 Jul 2015 09:20:10 -0700
Message-ID: <CABkgnnW_RaqzvB1=45xHpUVC-99mt3aD8o8SvKQ0jszWUdc=tA@mail.gmail.com>
To: Mike West <mkwst@google.com>
Cc: Yoav Weiss <yoav@yoav.ws>, Richard Barnes <rbarnes@mozilla.com>, Anne van Kesteren <annevk@annevk.nl>, Adrian Hope-Bailie <adrian@hopebailie.com>, "Nottingham, Mark" <mnotting@akamai.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>
On 7 July 2015 at 05:10, Mike West <mkwst@google.com> wrote:
> If there's a clear solution for the caching problem (`key`), and we're just
> waiting for it to be deployed, then I'd prefer `Prefer`. :)

OK, let's try to put these in perspective.  Yes, Key is a solution to
the "problem" of caching Prefer (and other similar header fields).
But the problem only exists where there are multiple independent uses
of Prefer in the same request.  My current understanding is that there
isn't a whole lot of enthusiasm for taking on the complexity of Key,
but primarily because it's not actually clear that the problem is
serious enough to warrant solving.  In other words, the medicine could
be worse than the illness.

Please don't let this sort of minutiae stop you from doing the right thing.
Received on Tuesday, 7 July 2015 16:20:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:49 UTC