![]() There was mention that Google was in the process of changing the way secured connections are portrayed in Chrome. ![]() I expect the same is the case of Google Chrome itself. All outgoing requests act as HTTP → HTTPS automatically, which results in → ‘This site can’t be reached / 192.168.8.1 refused to connect. There is no such toggle in the latest browser update. In the case of Brave there was an option under ‘Privacy & security’ w/ a toggle to do that very behaviour. It mimicked the behaviour of the EFF’s HTTPS Everywhere browser extension/plugin from some time ago. Until recently mainstream browsers (eg: Chromium-based ones like Google’s Chrome) offered the capability to optionally forward insecure HTTP requests to HTTPS. ![]() I think you fundamentally misunderstand what’s happening here. Then why bring it up as a possible solution? ![]() Since most users use http rather than https for intranet connections, there is no need to use the domain. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |