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

Re: [Referrer] Adding a referrer attribute delivery mechanism

From: Mike West <mkwst@google.com>
Date: Thu, 12 Feb 2015 09:06:45 +0100
Message-ID: <CAKXHy=ea9N+VKaJyVmc=A_27kPz+tH=Dhz+FJiWx=mUM7_xYeA@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Brian Smith <brian@briansmith.org>, Francois Marier <francois@mozilla.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>
On Thu, Feb 12, 2015 at 8:59 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Thu, Feb 12, 2015 at 8:43 AM, Mike West <mkwst@google.com> wrote:
>> [...]
> By the way, before we add more attributes, there is this proposal outstanding:
>   https://www.w3.org/Bugs/Public/show_bug.cgi?id=26533
> With that proposal whenever we figure out something new to add to
> Request objects, it would get automatically exposed to all request
> contexts as a feature. That is probably a better idea long term.
> (It still doesn't help with the navigational bits we discussed, but
> neither does this.)

That looks reasonable to me, and would address this use case.
Francois, would you be willing to hop onto that bug and describe this
proposal to see how it might fit in with a more generic way of setting
Fetch attributes? That might substantially simplify the wiring-up I
noted earlier in the thread.


Mike West <mkwst@google.com>, @mikewest

Google Germany GmbH, Dienerstrasse 12, 80331 München, Germany,
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der
Gesellschaft: Hamburg, Geschäftsführer: Graham Law, Christine
Elizabeth Flores
(Sorry; I'm legally required to add this exciting detail to emails. Bleh.)
Received on Thursday, 12 February 2015 08:07:32 UTC

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