Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is extremely annoying. The VPN will switch DNS servers and macOS and Safari work fine, but Chrome will not find internal servers. I assumed it was just a cache, but this makes sense.


I was astonished at how this was handled on the issue tracker. It was closed as "works as designed" even though the design was the problem.

https://bugs.chromium.org/p/chromium/issues/detail?id=432236

(I'm obviously a bit biased on the matter because it affected me and cost me a silly amount of time to track down.)


They also removed support for mandatory features of HTTPS [0], as defined in RFC 2818. Not that I'm against the change /per se/, but there correct way to go about it is to change the standard.

They also claimed Firefox was doing the same thing, which is false and not really sufficient justification for not supporting things that MUST be supported.

[0] https://bugs.chromium.org/p/chromium/issues/detail?id=700354




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: