ephemer
CDCloudflare Developers
•Created by ephemer on 11/29/2024 in #workers-help
fetch behaviour doesn't match curl or fetch in node/browser
Sending the following signed request fails with 403 from a Worker but succeeds in the browser and node repl. (Note the example is time sensitive and will soon time out for all platforms.)
Why? How do I fix it?
The server has a very permissive CORS policy (enabling all domains).
Is there a way to debug which headers Cloudflare actually sends in the
fetch
request? The network panel in the Workers code console shows that the correct headers should be sent, but then again there is a big notice saying "Provisional headers are shown.", so it's hard to say for sure.50 replies