RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-07-26 22:57:34 +00:00
Code Issues Activity Actions

LibWeb/Fetch: Use tuple syntax for headers in spec comments

Browse source 
This is an editorial change in the Fetch spec.

See: b482186
This commit is contained in:
Linus Groh 2022-12-07 18:14:52 +00:00
parent b3b51a5001
commit 011f6a6cb4
2 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Userland/Libraries/LibWeb/Fetch/Infrastructure/HTTP/Headers.cpp
View file

@ -569,13 +569,13 @@ bool is_no_cors_safelisted_request_header_name(ReadonlyBytes header_name)
// https://fetch.spec.whatwg.org/#no-cors-safelisted-request-header
bool is_no_cors_safelisted_request_header(Header const& header)
{
// To determine whether a header header is a no-CORS-safelisted request-header, run these steps:
// To determine whether a header (name, value) is a no-CORS-safelisted request-header, run these steps:
// 1. If header’s name is not a no-CORS-safelisted request-header name, then return false.
// 1. If name is not a no-CORS-safelisted request-header name, then return false.
if (!is_no_cors_safelisted_request_header_name(header.name))
return false;
// 2. Return whether header is a CORS-safelisted request-header.
// 2. Return whether (name, value) is a CORS-safelisted request-header.
return is_cors_safelisted_request_header(header);
}