Cross-Site Request Forgery
Cross-Site Request Forgery countermeasures can be greatly simplified using request metadata provided by modern browsers.| words.filippo.io
1. Introduction| w3c.github.io
1. Introduction| wicg.github.io
Cross-Site Request Forgery countermeasures can be greatly simplified using request metadata provided by modern browsers.| words.filippo.io
This specification defines common infrastructure that other specifications can use to interact with browser permissions. These permissions represent a user's choice to allow or deny access to "powerful features" of the platform. For developers, the specification standardizes an API to query the permission state of a powerful feature, and be notified if a permission to use a powerful feature changes state.| www.w3.org
1. Introduction| Android Open Source Project
1. Introduction| wicg.github.io
1. Introduction| wicg.github.io
1. Introduction| privacycg.github.io
What can we do for all those servers out there that want to use HTTPS, but find that they can't.| lowentropy.net
1. Introduction| drafts.csswg.org
This spec requires large amounts of work to section it and word it in ways that are normative. It is currently a very rough draft.| wicg.github.io
HTML| html.spec.whatwg.org
1. Introduction| www.w3.org
1. | drafts.csswg.org
1. | drafts.csswg.org
1. Introduction| drafts.csswg.org
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
Introduction| webaudio.github.io
1. Introduction| wicg.github.io
1. Introduction| www.w3.org
There are plenty of use cases for embedding third-party content on a site, as well as local content that may not be in HTML. Perhaps you gave a talk and want to share your slides. Sometimes you want to reference a video that exists only on YouTube. Maybe you have…| Adrian Roselli
1. Introduction| wicg.github.io
HTML| html.spec.whatwg.org
1. Introduction| w3c.github.io
HTML| html.spec.whatwg.org
1. Introduction| drafts.csswg.org
1. Introduction| w3c.github.io
HTML| html.spec.whatwg.org
1. Background| drafts.csswg.org
1. Infrastructure| wicg.github.io
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
1. Introduction| w3c.github.io
1. Background| drafts.csswg.org
We call it pages, domains, servers, websites, internets and we hope the other party will understand. Maybe, maybe not, but that can always be cleared with the additional “wait, a server, don't you mean a website?” You can't just ask those questions when reading various specifications and technical documents, so they try to call things by their correct names and in a consistent manner. And they do it so well that terms like origin, site, same origin, same site, eTLD and public suffix are n...| www.michalspacek.com
2. Examples| www.w3.org
2. Examples| w3c.github.io
HTML| html.spec.whatwg.org
3. Referrer Policies| w3c.github.io
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
1. Introduction| www.w3.org
Attestation| w3c.github.io
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
1. Introduction| w3c.github.io
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
This specification defines common infrastructure that other specifications can use to interact with browser permissions. These permissions represent a user's choice to allow or deny access to "powerful features" of the platform. For developers, the specification standardizes an API to query the permission state of a powerful feature, and be notified if a permission to use a powerful feature changes state.| w3c.github.io
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
1. Introduction| w3c.github.io
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
HTML| html.spec.whatwg.org
