It's likely being retried on a lower level, similar to the sibling comment about CORS.
Dev tools are not intentionally hiding the retry from you; from its perspective it's asking the networking layer to fetch a page, and the fact that that layer retries beneath the scenes is invisible to it.
Yeah, that was my thought as well. It threw me for a loop because I never would have expected that my browser dev tools would hide something like that. It was a core tenant of my debugging that was broken.
Comments
Really curious what the use case is for dev tools hiding a network request from you?
Sure, don't display it in the UI, but if the browser is retrying something I sure want to know about it when debugging!
Odd.
It's likely being retried on a lower level, similar to the sibling comment about CORS.
Dev tools are not intentionally hiding the retry from you; from its perspective it's asking the networking layer to fetch a page, and the fact that that layer retries beneath the scenes is invisible to it.
Yeah, that was my thought as well. It threw me for a loop because I never would have expected that my browser dev tools would hide something like that. It was a core tenant of my debugging that was broken.
The same happens with CORS preflight requests. https://httptoolkit.tech/blog/chrome-79-doesnt-show-cors-pre...