-
If I refresh a page particularly if it is still loading I get a 502 error. Is there any way I can capture exceptions and prevent the 502 from being seen in the browser? The errors can be any of these:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Refreshing a page that's still loading results in the current requests being cancelled and possibly the connections being aborted (HTTP/1.x). We listen to these cancelation events and cancel the proxy requests as well which triggers the error handling logic and the 502s. However, you shouldn't see the 502s in that case sense the client canceled and created new requests. Future requests should not be affected. That last InvalidOperationException "Stream was already consumed." is surprising. That implies a race condition in the abort logic. Needs investigation. |
Beta Was this translation helpful? Give feedback.
Refreshing a page that's still loading results in the current requests being cancelled and possibly the connections being aborted (HTTP/1.x). We listen to these cancelation events and cancel the proxy requests as well which triggers the error handling logic and the 502s. However, you shouldn't see the 502s in that case sense the client canceled and created new requests. Future requests should not be affected.
That last InvalidOperationException "Stream was already consumed." is surprising. That implies a race condition in the abort logic.
Needs investigation.