W3C home > Mailing lists > Public > public-webappsec@w3.org > November 2014

Re: [CSP] Clarifications regarding the HTTP LINK Header

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 14 Nov 2014 10:22:22 +0100
Message-ID: <CADnb78iau745byXPkLtPnGi3W0ivBocQJiSp0R_8A3pFtp+=8w@mail.gmail.com>
To: Brian Smith <brian@briansmith.org>
Cc: Ilya Grigorik <ilya@igvita.com>, Boris Zbarsky <bzbarsky@mit.edu>, "public-webappsec@w3.org" <public-webappsec@w3.org>
On Fri, Nov 14, 2014 at 4:05 AM, Brian Smith <brian@briansmith.org> wrote:
> The syntax ("http-equiv") literally says they are equivalent!

Yes, but the feature is defined in a very different way. The name is
legacy, as so many names throughout the platform. E.g. <meta
http-equiv=access-control-allow-origin content=*> must not work.


-- 
https://annevankesteren.nl/
Received on Friday, 14 November 2014 09:22:49 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:08 UTC