Skip to content

Fix check of request initiator being "fetch" #663

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

Merged
merged 1 commit into from
Oct 14, 2024
Merged

Fix check of request initiator being "fetch" #663

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 5 additions & 5 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4350,12 +4350,12 @@ this algorithm returns normally if compilation is allowed, and throws a
1. If |request|'s [=request/initiator=] is "`prefetch`" or "`prerender`",
return `default-src`.

2. If |request|'s <a for="request">initiator</a> is "`fetch`" or its
<a for="request">destination</a> is "", return `connect-src`.

3. Switch on |request|'s <a for="request">destination</a>, and execute
2. Switch on |request|'s <a for="request">destination</a>, and execute
the associated steps:

: the empty string
::
1. Return `connect-src`.
: "`manifest`"
::
1. Return `manifest-src`.
Expand Down Expand Up @@ -4409,7 +4409,7 @@ this algorithm returns normally if compilation is allowed, and throws a
::
1. Return null.

4. Return `connect-src`.
3. Return `connect-src`.

Note: The algorithm returns `connect-src` as a default fallback. This is
intended for new fetch destinations that are added and which don't explicitly
Expand Down
Loading