zlacker

What cripples FF DevTools for me is being unable to find the setting for timeout on HTTP GET, during full-stack development. If I've set a breakpoint in a debugger on my server and proceed to single-step there, FF aborts the GET request with an error. So client-side JS doesn't see the eventual result of the GET, it has to recover from the error to proceed, e.g. by a full page-reload.

Chromium, last I tried it, by default sets the necessary HTTP timeout(s) to infinity if its DevTools is open.

My searches of Firefox docs/wiki, StackExchange, HN Algolia for a fix have come up empty.

Navigating to "about:config" and searching for "timeout" finds 27 different settings prefixed with the substring "network". Some are obviously in units of milliseconds, others perhaps whole seconds.

Anyone know which one (or what combination) might incant the necessary black magic?