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
When a server-side load function makes a request to the same hostname (not necessarily the same domain) and includes additional headers with the Headers object instead of a regular object, these additional headers are replaced with a Cookie header.
There are two issues to address:
Overwritten headers if they are passed as a Headers object
Incorrect detection of similar hostnames (ports aren't considered)
Actually, it seems like the ports should not be considered, according to RFC 6265:
Similarly, cookies for a given host are shared
across all the ports on that host, even though the usual "same-origin
policy" used by web browsers isolates content retrieved via different
ports.
Describe the bug
When a server-side
load
function makes a request to the same hostname (not necessarily the same domain) and includes additional headers with theHeaders
object instead of a regular object, these additional headers are replaced with aCookie
header.There are two issues to address:
Headers
objectReproduction
https://github.com/illright/sveltekit-repro-headers-class
Logs
System Info
Severity
blocking all usage of SvelteKit
Additional Information
No response
The text was updated successfully, but these errors were encountered: