Can confirm. I just spent many hours trying to diagnose why an API was timing out. Turns out Snort blocked the IP address of the certificate authority which chr

Can confirm. I just spent many hours trying to diagnose why an API was timing out. Turns out Snort blocked the IP address of the certificate authority which chrome was secretly using to verify the API's certificate. My local machine had the verification cached but the docker container I was using did not. No indication of what was going on in the top-level network tools; I had to use the hard-to-find network diagnostics recorder in Chrome to even realize chrome was connecting to the certificate authority.