Re: [whatwg/fetch] New Proposal: Fetch retry (Issue #1838)

rakina left a comment (whatwg/fetch#1838)

OK, but the fact that the fetch is not retried doesn't imply it's because of policy errors. It can be caused by any other remaining errors e.g. improper settings on the server?

Other alternatives if that is still the concern is to add some random delay in resolving (either always or randomly), or just to never let the fetch resolve with errors at all if the retry option is set (which is fine for the main case here, sending beacons). Do you think those mitigate the concerns there?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1838#issuecomment-3019452794
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1838/3019452794@github.com>