Worker 403 error with custom headers, worked fine a few weeks ago
I am using a worker as a proxy to bypass CORS. When using it without custom headers, it doesn't fetch anything and returns the correct response. When used with custom headers (urlToFetch), it used to correctly return the fetched content. But now it returns this instead:
The response headers of the request contain
server: cloudflare
I haven't changed the worker configuration in 6 months. It was working fine all this time, but now it gives this error.
6 Replies
That looks like an upstream server error. Is your worker making a sub request?
yes, the worker is making a sub request, it's just fetching a link and returning it's contents
for more context: requests are being sent to the worker from a github pages site
Sounds like that link might have broken
The link works fine in the browser though
As it always did
Host might be blocking workers then. It is not uncommon
yeah, you were correct