Skip to content

Issue #181 - Redefine network request in terms of Fetch #182

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.

Sign up for GitHub

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

Open
wants to merge 5 commits into
base: gh-pages
Choose a base branch
from
Open

Issue #181 - Redefine network request in terms of Fetch #182

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
c1a5ceb
Issue #181 - redefine section 3.1 in terms of Fetch
miketaylr Feb 6, 2025
b238793
Fetch updates from 3.1 to section 5.3
miketaylr Feb 6, 2025
efbce4a
minor edits to intro; link to ABNF rfc
miketaylr Feb 7, 2025
35a7a96
review feedback
miketaylr Feb 17, 2025
b48ee03
manually cite http-network fetch
miketaylr Feb 17, 2025
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
69 changes: 26 additions & 43 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
github: "https://github.com/w3c/network-error-logging/",
shortname: "network-error-logging",
specStatus: "ED",
xref: ["network-reporting", "fetch", "hr-time", "html", "referrer-policy", "reporting", "resource-timing", "secure-contexts", "url"],
xref: ["network-reporting", "fetch", "hr-time", "html", "infra", "mixed-content", "referrer-policy", "reporting", "resource-timing", "secure-contexts", "url"],
editors: [{
name: "Douglas Creager",
url: "https://dcreager.net/",
Expand Down Expand Up @@ -117,38 +117,20 @@ <h2>Network requests</h2>

<p>
A <dfn data-lt="network requests">network request</dfn> occurs when the
user agent must use the network to service a single
<dfn data-cite="RFC9110#core.semantics">request</dfn>.
[=user agent=] attempts to <a data-cite="fetch#http-network-fetch">HTTP-network fetch</a>
a resource over the network for a given [=request=].
</p>

<p>
If the user agent can service a <a>request</a> out of a local
cache, that <a>request</a> MUST NOT result in a <a>network
request</a>.
A [=request=] MUST NOT result in a <a>network request</a> if the user
agent is known to be offline (i.e., when <code>navigator.</code>
{{NavigatorOnLine/onLine}} returns <code>false</code>).
</p>

<p>
If the user agent follows [=redirect status|redirects=] as part of a [=navigate|navigation=],
there MUST be separate <a>network requests</a> for each <a>request</a> in
the redirect chain.
</p>

<p>
A <a>request</a> MUST NOT result in a <a>network request</a> if the user
agent is known to be offline (i.e., when <code>navigator.</code>{{NavigatorOnLine/onLine}} returns
<code>false</code>).
</p>

<p>
A <a>request</a> MUST NOT result in a <a>network request</a> if it is
blocked due to mixed content or CORS failures. Any <a>CORS-preflight
request</a> MUST result in its own <a>network request</a>.
</p>

<p class="note">
For user agents that service <a>requests</a> according to the [[FETCH]]
standard, a <a>network request</a> corresponds to one execution of the
<a data-cite="FETCH#http-network-fetch">HTTP-network fetch</a> algorithm.
A [=request=] MUST NOT result in a <a>network request</a> if it is
blocked due to [=mixed content=] or [=CORS protocol|CORS=] failures. Any
[=CORS-preflight request=] MUST result in its own <a>network request</a>.
</p>

<p>
Expand All @@ -160,9 +142,9 @@ <h2>Network requests</h2>
<ol>
<li>
<dfn>DNS resolution</dfn>: The user agent uses the Domain Name System
[[RFC1034]] to resolve a domain name into an IP address of a
[[RFC1034]] to resolve a domain name into an [=IP address=] of a
<dfn data-cite="RFC9110#core.semantics">server</dfn> can that service
HTTP requests to that domain.
HTTP [=requests=] to that domain.
</li>

<li>
Expand All @@ -173,8 +155,8 @@ <h2>Network requests</h2>

<li>
<dfn>Transmission of request and response</dfn>: Once the secure
channel is established, the user agent can transmit the HTTP request,
and receive the response from the <a>server</a>.
channel is established, the user agent can transmit the HTTP
[=request=], and receive the [=response=] from the <a>server</a>.
</li>
</ol>

Expand All @@ -186,8 +168,8 @@ <h2>Network requests</h2>
to the same domain. Similarly, HTTP
<a data-cite="RFC9112#persistent.connections">persistent connections</a>
allow open connections to be shared for multiple requests to the same
<a>origin</a>. However, if multiple <a>phases</a> occur, they will occur
in the above order.
[=network partition key=]. However, if multiple <a>phases</a> occur, they
will occur in the above order.
</p>

<p class="ednote">
Expand Down Expand Up @@ -298,8 +280,8 @@ <h2>NEL policies</h2>

<p>
Each <a>NEL policy</a> has a <dfn>received IP address</dfn>, which is the
IP address of the <a>server</a> that the user agent received this <a>NEL
policy</a> from.
[=IP address=] of the <a>server</a> that the user agent received this
<a>NEL policy</a> from.
</p>

<p>
Expand Down Expand Up @@ -412,7 +394,7 @@ <h2><code>NEL</code> response header</h2>
<p>
The <dfn><code>NEL</code></dfn> <a>response header</a> is used to
communicate an <a>origin</a>'s <a>NEL policy</a> to the user agent. The
ABNF (Augmented Backus-Naur Form) syntax for the <a>NEL</a> header is as
ABNF (Augmented Backus-Naur Form) [[RFC5234]] syntax for the <a>NEL</a> header is as
follows:
</p>

Expand Down Expand Up @@ -591,7 +573,8 @@ <h2>Process policy headers</h2>

<li>
Let <var>key</var> be the result of calling <a>determine the network
partition key</a>, given <var>request</var>.
partition key</a>, given <var>request</var>'s
[=request/reserved client=].
</li>

<li>
Expand Down Expand Up @@ -660,7 +643,7 @@ <h2>Process policy headers</h2>
<dl>
<dt><a>received IP address</a></dt>
<dd>
the IP address of the <a>server</a> that the user agent received
the [=IP address=] of the <a>server</a> that the user agent received
<var>response</var> from

<p class="ednote">
Expand Down Expand Up @@ -742,7 +725,8 @@ <h2>Choose a policy for a request</h2>

<li>
Let <var>key</var> be the result of calling <a>determine the network
partition key</a>, given <var>request</var>.
partition key</a>, given <var>request</var>'s'
[=request/reserved client=].
</li>

<li>
Expand Down Expand Up @@ -814,10 +798,9 @@ <h2>Extract request headers</h2>

<li>
For each <var>header</var> in <var>request</var>'s
[=request/header list=] whose <a
data-lt="header name">name</a> is <var>header name</var>, append
<var>header</var>'s <a data-lt="header value">value</a> to
<var>values</var>.
[=request/header list=] whose <a data-lt="header name">name</a>
is <var>header name</var>, append <var>header</var>'s
<a data-lt="header value">value</a> to <var>values</var>.
</li>

<li>
Expand Down