From c1a5cebe5c01d9a9f6523c23232a729aa3822077 Mon Sep 17 00:00:00 2001
From: Mike Taylor
A network request occurs when the
- user agent must use the network to service a single
- request.
+ user agent must use the network to service a single [=request=].
- If the user agent can service a request out of a local
- cache, that request MUST NOT result in a network
- request.
+ If the user agent can service a [=request=] out of a local cache, that
+ [=request=] MUST NOT result in a network request.
- If the user agent follows [=redirect status|redirects=] as part of a [=navigate|navigation=],
- there MUST be separate network requests for each request in
- the redirect chain.
+ If the user agent follows [=redirect status|redirects=] as part of a
+ [=navigate|navigation=], there MUST be separate network requests
+ for each request in the redirect chain.
- A request MUST NOT result in a network request if the user
- agent is known to be offline (i.e., when
- A request MUST NOT result in a network request if it is
- blocked due to mixed content or CORS failures. Any CORS-preflight
- request MUST result in its own network request.
-
- For user agents that service requests according to the [[FETCH]]
- standard, a network request corresponds to one execution of the
- HTTP-network fetch algorithm.
+ A [=request=] MUST NOT result in a network request if it is
+ blocked due to [=mixed content=] or [=CORS protocol|CORS=] failures. Any
+ [=CORS-preflight request=] MUST result in its own network request.
@@ -160,9 +152,9 @@ Network requests
navigator.
{{NavigatorOnLine/onLine}} returns
- false
).
+ A [=request=] MUST NOT result in a network request if the user
+ agent is known to be offline (i.e., when navigator.
+ {{NavigatorOnLine/onLine}} returns false
).
Network requests
@@ -186,8 +178,8 @@ Network requests
Network requests
to the same domain. Similarly, HTTP
persistent connections
allow open connections to be shared for multiple requests to the same
- origin. However, if multiple phases occur, they will occur
- in the above order.
+ [=network partition key=]. However, if multiple phases occur, they
+ will occur in the above order.
From b23879392913ccd4d000ede8a6871441ef6a5007 Mon Sep 17 00:00:00 2001
From: Mike Taylor
Each NEL policy has a received IP address, which is the
- IP address of the server that the user agent received this NEL
- policy from.
+ [=IP address=] of the server that the user agent received this
+ NEL policy from.
@@ -583,7 +583,8 @@
@@ -734,7 +735,8 @@
A network request occurs when the
- user agent must use the network to service a single [=request=].
+ [=user agent=] attempts to [=fetch=] a resource over the network for a
+ given [=request=].
@@ -404,7 +405,7 @@
The
A network request occurs when the
- [=user agent=] attempts to [=fetch=] a resource over the network for a
- given [=request=].
-
- If the user agent can service a [=request=] out of a local cache, that
- [=request=] MUST NOT result in a network request.
-
- If the user agent follows [=redirect status|redirects=] as part of a
- [=navigate|navigation=], there MUST be separate network requests
- for each request in the redirect chain.
+ [=user agent=] attempts to [=HTTP-network fetch=] a resource over the
+ network for a given [=request=].
From b48ee03a40cf3df24fd01e80c1f1ccff99c017ec Mon Sep 17 00:00:00 2001
From: Mike Taylor
A network request occurs when the
- [=user agent=] attempts to [=HTTP-network fetch=] a resource over the
- network for a given [=request=].
+ [=user agent=] attempts to HTTP-network fetch
+ a resource over the network for a given [=request=].
From 20b68d2b6cf69f693e64323c325cd135dc27371d Mon Sep 17 00:00:00 2001
From: Mike Taylor
+ For user agents that service requests according to the [[FETCH]]
+ standard, a network request corresponds to one execution of the
+ HTTP-network fetch algorithm.
+
Regardless of which fetch algorithm and which underlying application and
transport protocols are used, servicing a network request consists
NEL policies
Process policy headers
Process policy headers
Choose a policy for a request
Extract request headers
Network requests
NEL
response headerNEL
response header is used to
communicate an origin's NEL policy to the user agent. The
- ABNF (Augmented Backus-Naur Form) syntax for the NEL header is as
+ ABNF (Augmented Backus-Naur Form) [[RFC5234]] syntax for the NEL header is as
follows:
Network requests
Network requests
Network requests
[=CORS-preflight request=] MUST result in its own network request.