Not really... I don't even remember `about:config`. I know of its existence, but is it `config`, `:config`, or `about`, or ...? So what I do is, I google, righ

Not really... I don't even remember `about:config`. I know of its existence, but is it `config`, `:config`, or `about`, or ...? 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).