EdgeResponse Status 499 -- Requesting Client Expected Responses
Hello all, I have a strange scenario that I have been researching the Cloudflare doc's with AI to try and understand, but I keep going in circles and I am curious if others have faced the same scenario.
We have a client who reaches out to us frequently via API to our endpoints that are front ended by Cloudflare. 99.9% of traffic is processing correctly and without issue, but occasionally the clients request is being terminated in <1s. Our clients software has been coded for unexpected responses to perform a follow up 'find' request against our system to check the status. However, because the initial request was terminated so quickly the follow up find request is taking place within 1s from the original request which is too quick for the original request to complete and results in our client running duplicate requests.
From our perspective this is being recorded in Cloudflare HTTP logs as a 499 early client termination EdgeResponseStatus and feels out of our control.
What should be expected on a client's end when a request is getting interrupted/disconnected between the client and the Cloudflare edge? An empty response?
Is there any way to control a default response if nothing is returned from the origin server or cloudflare?
We have a client who reaches out to us frequently via API to our endpoints that are front ended by Cloudflare. 99.9% of traffic is processing correctly and without issue, but occasionally the clients request is being terminated in <1s. Our clients software has been coded for unexpected responses to perform a follow up 'find' request against our system to check the status. However, because the initial request was terminated so quickly the follow up find request is taking place within 1s from the original request which is too quick for the original request to complete and results in our client running duplicate requests.
From our perspective this is being recorded in Cloudflare HTTP logs as a 499 early client termination EdgeResponseStatus and feels out of our control.
What should be expected on a client's end when a request is getting interrupted/disconnected between the client and the Cloudflare edge? An empty response?
Is there any way to control a default response if nothing is returned from the origin server or cloudflare?
