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:

We are sorry !

The page or file you requested is not accessible. Please try after some time.

Reference 18.ae293417.1729453716.138d65bc

We are sorry !

The page or file you requested is not accessible. Please try after some time.

Reference 18.ae293417.1729453716.138d65bc

The response headers of the request contain

server: cloudflare

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.

Ttimepassuser I am using a worker as a proxy to bypass CORS. When using it without custom head...

Cyb3r-Jak3•10/20/24, 9:57 PM

That looks like an upstream server error. Is your worker making a sub request?

CCyb3r-Jak3 That looks like an upstream server error. Is your worker making a sub request?

timepassuserOP•10/20/24, 9:59 PM

yes, the worker is making a sub request, it's just fetching a link and returning it's contents

timepassuserOP•10/20/24, 9:59 PM

for more context: requests are being sent to the worker from a github pages site

Ttimepassuser yes, the worker is making a sub request, it's just fetching a link and returning...

Cyb3r-Jak3•10/20/24, 10:28 PM

Sounds like that link might have broken

CCyb3r-Jak3 Sounds like that link might have broken

timepassuserOP•10/20/24, 10:29 PM

The link works fine in the browser though

timepassuserOP•10/20/24, 10:29 PM

As it always did

Cyb3r-Jak3•10/20/24, 11:22 PM

Host might be blocking workers then. It is not uncommon

CCyb3r-Jak3 Host might be blocking workers then. It is not uncommon

timepassuserOP•10/21/24, 5:00 PM

yeah, you were correct