Here's a different take from a SvelteKit thread on the same subject: > because the cookie is set to

because the cookie is set to the domain of the worker
but you could use postMessage in your worker, and set the cookie with javascript instead
you cant set a cookie with headers from one domain for another