However I did find this really weird bug where Firefox was caching something to do with sockets (that would disallow connecting a new socket) that could only be cleared by restarting Firefox itself.
Is that http2? Cause http2 allows for reuse of a connection for additional requests.
This caught me out with envoy reverse proxy doing a few subdomains using a wildcard cert.
The browser would reuse the connection cause the cert authority and IP was the same, but envoy couldn’t figure out how to route the request correctly. Absolute head scratcher!
In most cases yes.
However I did find this really weird bug where Firefox was caching something to do with sockets (that would disallow connecting a new socket) that could only be cleared by restarting Firefox itself.
Is that http2? Cause http2 allows for reuse of a connection for additional requests.
This caught me out with envoy reverse proxy doing a few subdomains using a wildcard cert.
The browser would reuse the connection cause the cert authority and IP was the same, but envoy couldn’t figure out how to route the request correctly. Absolute head scratcher!