504 Gateway timeout
Hello, I have a simple CF worker, it takes in a request, checks if it exists in cache.match(), if yes, then return that, if not, then it gets sent to my backend, that response gets put into cache (cache-control comes from backend) and returned.
Everything worked like it should for a while, but suddenly I am now getting 504 Gateway timeout for some requests, even though Origin server is completely healthy.
The 504 error has cache HIT in response headers and it also has a age header that keeps going up. It gets sent back immidiately (request never makes it to origin server).
Any help regards debugging this would be helpful! Is there some kind of special cache logic in CF regards this?
0 Replies