You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ASCII serialisation of an origin algorithm referenced in Step 2. does not handle the case of a "client" origin. (Because it is about serializing an origin as described in the HTML spec, not a request's origin as described in the fetch spec.)
How should an origin of "client" be serialized?
The text was updated successfully, but these errors were encountered:
What is the issue with the Fetch Standard?
When
serializing a request origin
, Step 2. tells us toReturn request's origin, serialized
. A request's origin is either"client"
or an Origin. However, theASCII serialisation of an origin
algorithm referenced in Step 2. does not handle the case of a"client"
origin. (Because it is about serializing an origin as described in the HTML spec, not a request's origin as described in the fetch spec.)How should an origin of
"client"
be serialized?The text was updated successfully, but these errors were encountered: