Share this article
Latest news
With KB5043178 to Release Preview Channel, Microsoft advises Windows 11 users to plug in when the battery is low
Copilot in Outlook will generate personalized themes for you to customize the app
Microsoft will raise the price of its 365 Suite to include AI capabilities
Death Stranding Director’s Cut is now Xbox X|S at a huge discount
Outlook will let users create custom account icons so they can tell their accounts apart easier
Google Chrome tests Balanced HTTPS-First Mode for fewer Warnings
Chrome’s new Balanced mode for HTTPS warnings
3 min. read
Published onJune 29, 2024
published onJune 29, 2024
Share this article
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Google has enabled HTTPS-First Mode by default in Chrome for some time now. The company, which takes security seriously in Chrome and always tries to use secure connections, is testing a new “Balanced HTTPS-First Mode” to reduce the number of warnings and make browsing less annoying.
Google is also working on other HTTPS-First Mode features, including:
By default, browsing the web doesn’t automatically use HTTPS encryption. This means that the information you send and receive might be vulnerable to interception.
HFM (HTTPS-First Mode) tries to upgrade all connections to HTTPS whenever possible. This ensures your data is encrypted and more secure. However, some websites might not have a working HTTPS version, leading to connection errors and frustration.
Note: You can confirm whether HTTPS-First Mode (HFM) is enabled by visiting Settings > Privacy and Security > Advanced. There, you’ll notice that the ‘Always use secure connections’ toggle is enabled by default.
Chrome’s HTTPS-First Balanced Mode
A new flag, correspondingcommit, andbugspotted by Windows Report indicates Google is working on “Balanced HTTPS-First Mode.” When enabled, it “uses HTTPS-First Mode only when secure connections are likely possible.” The flag is also available on Android and Windows, Mac, Linux, and Chrome OS platforms.
This new mode aims to strike a balance between security and user experience. Instead of forcing HTTPS everywhere, it will only warn you when a secure connection seems likely but isn’t used. This reduces the number of frustrating connection errors while still promoting secure connections.“Add feature and flag for balanced Ask-Before-HTTP (nee HFM). Balanced mode will warn when we can reasonably expect a connection to support HTTPS, but not when we can’t. This is obviously less secure than full HFM, but will limit warning fatigue and evolve over time as HTTPS is possible in more scenarios,” Google notes.
Benefits of Balanced HTTPS-First Mode:Enhanced Security: You’ll still get warnings for potentially insecure connections, protecting your data from snooping.Reduced Warning Fatigue: No more annoying errors for websites that genuinely don’t support HTTPS.Future-Proof: As more websites switch to HTTPS, the warnings will become even rarer.
Additionally,Chrome will offer performance suggestions when tabs consume more resourcesandGoogle is making Chrome on Windows to use ARM processors for video processing that improves battery life.
More about the topics:Chrome
Venkat
Tech Journalist
Venkat, an experienced tech writer from India, specializes in uncovering new web browser features and tech trends. His work bridges the gap between technology and its users, making the digital world more accessible.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Venkat
Tech Journalist
Venkat is an experienced tech writer who specializes in uncovering new web browser features and tech trends.