So what I do is, I google, right? First page that comes up references how to fix the problem on both Firefox and Chromium-based browsers.
So on Firefox, I have to type the config page, then search for ocsp, then disable it. Then, I can finally access the webpage, but of course, I should remember to re-enable it after I'm done on the misconfigured server.
On Chrome, I can fire up an incognito window, type a magic keyword, do what I need, close the incognito window and go back to default.
Honestly, the latter is a vastly better experience in my world (I do backend/integration dev, mostly Python nowadays, probably a FE engineer will not care either way).
You can do the same on Firefox (at least developer edition). I thought that you want to do that without going to incognito mode.
It's a great hidden feature just like Firefox has shift+right click/double right click opening the native context. No amount of "well you can just put this in the console in these cases or this in the console in those cases" makes these kinds of features any less useful.