38 ms·
I don't think the meta version of Permissions-Policy ever got implemented. "http-equiv" isn't a magic "here's a HTTP header I forgot to mention" pixie dust. Be
by pdenton 5y ago
I don't think the meta version of Permissions-Policy ever got implemented. "http-equiv" isn't a magic "here's a HTTP header I forgot to mention" pixie dust.
Better stick to the actual recommendation of adding the header in the server configuration.
- imwillofficial 5y agoIn my case I don’t have access to the server configuration. I’m running a blog with Ghost Pro, is the above a reasonable workaround?
- shakna 5y agoWhilst http-equiv is said to be an enumerated value, so far as I know in Chrome, it actually is "magic HTTP Header pixie dust": [0] And whilst in Firefox parsing of the element is more spread out, they accept a very wide number of headers that aren't documented, and you'll find examples on MDN for any number of headers using http-equiv which aren't specified in the standard or on their docs for http-equiv itself [2] (For example, X-DNS-Prefetch-Control [1]). [0] https://source.chromium.org/chromium/chromium/src/+/master:out/Debug/gen/third_party/blink/renderer/bindings/core/v8/v8_html_meta_element.cc;l=95;drc=65edd51497213d077fa26bb4f24ab2341b243074;bpv=1;bpt=1?q=metaelement.c&ss=chromium https://source.chromium.org/chromium/chromium/src/+/master:o... [1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-DNS-Prefetch-Control https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-... [2] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta#attr-http-equiv https://developer.mozilla.org/en-US/docs/Web/HTML/Element/me...