3 ms·
Had to deal with a firewall that filtered all unknown/"new" HTTP headers. This included CORS. A PITA to find the reason why Firefox wouldn't use the Google fon
by stesch 8y ago
Had to deal with a firewall that filtered all unknown/"new" HTTP headers. This included CORS.
A PITA to find the reason why Firefox wouldn't use the Google fonts.
- crooked-v 8y agoThat kind of crapware is why I'm increasingly glad that the http specs are moving towards being completely illegible to middleware boxes.
- edoceo 8y agoHow would http be any harder for middleware than app-layer? If both linked to libhttp.c, couldn't they each get the full parsing/reading/writing - wether proxy or server?
- crooked-v 8y agoBeing able to parse HTTP doesn't get anywhere when you can't actually get at the contents because they're encrypted (as with all major HTTP2 implementations).
- stesch 8y agohttps://www.howtoforge.com/filtering-https-traffic-with-squid https://www.howtoforge.com/filtering-https-traffic-with-squi... http://www.watchguard.com/help/docs/wsm/xtm_11/en-us/content/en-us/certificates/cert_https_proxy_resign_c.html http://www.watchguard.com/help/docs/wsm/xtm_11/en-us/content...