Skip to content
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

RFC6265bis: Offload Service Worker SFC computation to spec #2217

Merged
merged 6 commits into from
Jul 27, 2022
Merged

RFC6265bis: Offload Service Worker SFC computation to spec #2217

Changes from 3 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
ffd71c8
Offload Service Worker SFC computation to spe
sbingler Jul 7, 2022
923a21c
Merge branch 'httpwg:main' into Issue1288
sbingler Jul 13, 2022
706b78f
Add to change log
sbingler Jul 13, 2022
2d214ab
Offload Service Worker SFC computation to spe
sbingler Jul 7, 2022
a0c3bfa
Add to change log
sbingler Jul 13, 2022
d5c4a4c
Merge branch 'httpwg-main' into Issue1288
sbingler Jul 14, 2022
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
19 changes: 5 additions & 14 deletions draft-ietf-httpbis-rfc6265bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1084,20 +1084,8 @@ Service Workers are more complicated, as they act as a completely separate
execution context with only tangential relationship to the Document which
registered them.

Requests which simply pass through a Service Worker will be handled as described
above: the request's client will be the Document or Worker which initiated the
request, and its "site for cookies" will be those defined in
{{document-requests}} and {{dedicated-and-shared-requests}}

Requests which are initiated by the Service Worker itself (via a direct call to
`fetch()`, for instance), on the other hand, will have a client which is a
ServiceWorkerGlobalScope. Its "site for cookies" will be the Service Worker's
URI's origin.

Given a ServiceWorkerGlobalScope (`worker`), the following algorithm returns its
"site for cookies":

1. Return `worker`'s origin.
How user agents handle Service Workers may differ, but user agents SHOULD
match the {{SERVICE-WORKERS}} specification.

## Ignoring Set-Cookie Header Fields {#ignoring-cookies}

Expand Down Expand Up @@ -2512,6 +2500,9 @@ The "Cookie Attribute Registry" should be created with the registrations below:
* Add note not to send invalid cookies due to public suffix list changes:
<https://github.com/httpwg/http-extensions/pull/2215>

* Add note regarding Service Worker's computation of "site for cookies":
<https://github.com/httpwg/http-extensions/pull/2217>

# Acknowledgements
{:numbered="false"}
RFC 6265 was written by Adam Barth. This document is an update of RFC 6265,
Expand Down