Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FF87 Preference for credentials in CORS preflight request #2558

Merged
merged 17 commits into from
Mar 2, 2021
Merged
Show file tree
Hide file tree
Changes from 16 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions files/en-us/mozilla/firefox/releases/87/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,10 @@ <h4 id="Removals_4">Removals</h4>

<h3 id="HTTP">HTTP</h3>

<ul>
hamishwillee marked this conversation as resolved.
Show resolved Hide resolved
<li>Some enterprise authentication services require that TLS client certificates be <a href="/en-US/docs/Web/HTTP/CORS#Preflight_requests_and_credentials">sent in CORS preflight requests</a>. Users of these services can enable this (non-specification compliant) behavior using the <code>network.cors_preflight.allow_client_cert</code> preference ({{bug(1511151)}}).</li>
</ul>

<h4 id="Removals_5">Removals</h4>

<h3 id="Security">Security</h3>
Expand Down
4 changes: 2 additions & 2 deletions files/en-us/web/api/fetch_api/basic_concepts/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,9 @@

<h2 id="In_a_nutshell">In a nutshell</h2>

<p>At the heart of Fetch are the Interface abstractions of HTTP {{domxref("Request")}}s, {{domxref("Response")}}s, {{domxref("Headers")}}, and {{domxref("Body")}} payloads, along with a {{domxref("GlobalFetch.fetch","global fetch")}} method for initiating asynchronous resource requests. Because the main components of HTTP are abstracted as JavaScript objects, it is easy for other APIs to make use of such functionality.</p>
<p>At the heart of Fetch are the Interface abstractions of HTTP {{domxref("Request")}}s, {{domxref("Response")}}s, {{domxref("Headers")}}, and {{domxref("Body")}} payloads, along with a {{domxref("WindowOrWorkerGlobalScope/fetch","global fetch")}} method for initiating asynchronous resource requests. Because the main components of HTTP are abstracted as JavaScript objects, it is easy for other APIs to make use of such functionality.</p>

<p><a href="/en-US/docs/Web/API/ServiceWorker_API">Service Workers</a> is an example of an API that makes heavy use of Fetch.</p>
<p><a href="/en-US/docs/Web/API/Service_Worker_API">Service Workers</a> is an example of an API that makes heavy use of Fetch.</p>

<p>Fetch takes the asynchronous nature of such requests one step further. The API is completely {{jsxref("Promise")}}-based.</p>

Expand Down
16 changes: 5 additions & 11 deletions files/en-us/web/api/fetch_api/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -36,23 +36,17 @@ <h3 id="Differences_from_jQuery">Differences from jQuery</h3>

<ul>
<li>The Promise returned from <code>fetch()</code> <strong>won’t reject on HTTP error status</strong> even if the response is an HTTP <code>404</code> or <code>500</code>. Instead, it will resolve normally (with <code>ok</code> status set to <code>false</code>), and it will only reject on network failure or if anything prevented the request from completing.</li>
<li><code>fetch()</code> can receive cross-site cookies; you can establish a cross-site session using fetch.</li>
<li><code>fetch()</code> <strong>won’t send cookies</strong>, unless you set <code>credentials: 'same-origin'</code>.
<li><code>fetch()</code> <strong>won’t send cross-origin cookies</strong> unless you set the <em>credentials</em> <a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/fetch#parameters">init option</a> (to <code>include</code>).
<ul>
<li>In <a href="https://github.com/whatwg/fetch/pull/585" rel="nofollow noopener">August 2017</a>, the spec changed the default credentials policy to <code>'same-origin'</code>. The following browsers shipped an outdated native fetch, and were updated in these versions:
<ul>
<li>Firefox version 61.0b13.</li>
<li>Safari version 12.</li>
<li>Chrome version 68.</li>
</ul>
</li>
<li>In <a href="https://github.com/whatwg/fetch/pull/585" rel="nofollow noopener">April 2018</a>, the spec changed the default credentials policy to <code>'same-origin'</code>. The following browsers shipped an outdated native fetch, and were updated in these versions: Firefox 61.0b13, Safari 12, Chrome 68.</li>
<li>If you are targeting older versions of these browsers, be sure to include <code>credentials: 'same-origin'</code> <a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/fetch#parameters">init option</a> on all api requests that may be affected by cookies/user login state.</li>
</ul>
</li>
</ul>

<div class="note">
<p><strong>Note</strong>: Find out more about using the Fetch API features in <a href="/en-US/docs/Web/API/Fetch_API/Using_Fetch">Using Fetch</a>, and study concepts in <a href="/en-US/docs/Web/API/Fetch_API/Basic_concepts">Fetch basic concepts</a>.</p>
<div class="notecard note">
<h4>Note</h4>
<p>Find out more about using the Fetch API features in <a href="/en-US/docs/Web/API/Fetch_API/Using_Fetch">Using Fetch</a>, and study concepts in <a href="/en-US/docs/Web/API/Fetch_API/Basic_concepts">Fetch basic concepts</a>.</p>
</div>

<h3 id="Aborting_a_fetch">Aborting a fetch</h3>
Expand Down
Loading