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
In CORS-preflight fetch, preflight-request headers Access-Control-Request-Method and Access-Control-Request-Headers are appended to the preflight request's header list, e.g.
Append (Access-Control-Request-Method, request’s method) to preflight’s header list.
However, in section 3.4.2 of the draft report (more specifically, in step 10.2.1.1), request header Access-Control-Request-Private-Network is not appended to, but set in the preflight request's header list:
Set "Access-Control-Request-Private-Network" to "true" in preflight’s header.
I'm not sure whether this discrepancy is warranted. I believe it to be inconsequential (?) but, for consistency, adopting the Fetch standard's wording/operation (append rather than set) would perhaps be preferable.
The text was updated successfully, but these errors were encountered:
In CORS-preflight fetch, preflight-request headers
Access-Control-Request-Method
andAccess-Control-Request-Headers
are appended to the preflight request's header list, e.g.However, in section 3.4.2 of the draft report (more specifically, in step 10.2.1.1), request header
Access-Control-Request-Private-Network
is not appended to, but set in the preflight request's header list:I'm not sure whether this discrepancy is warranted. I believe it to be inconsequential (?) but, for consistency, adopting the Fetch standard's wording/operation (append rather than set) would perhaps be preferable.
The text was updated successfully, but these errors were encountered: