Questions about the settings for 'Upgrade connections to HTTPS' (technical questions not problem)

Default is ‘Standard’, can also be ‘Strict’
I’ve been running OK with the default, but I’d like to know more.

What exactly does it do under the covers for ‘Standard’ and also for ‘Strict’?
What is the benefit of ‘Strict’ or what circumstances make it more desirable?

Thank you.

We actually wrote a blog post about this:

Some further reading:

Hope this helps! Please let me know if you have any further questions.

@Mattches I think you linked to other topic. They were asking about the option to change for HTTPS, not for fingerprinting.

image

image

Verbiage differs depending on whether you’re looking at global settings or the widget for site specific.

That said, think were on the right track in regards to the blog.

@Meeker-Morgan short answer is this:

  • Strict = Only Connect with HTTPS: This means that it won’t ever allow websites to load in HTTP.

  • Standard = Upgrade connection to HTTPS: This will attempt to upgradethe connection to HTTPS if possible, but otherwise will give you the ability to proceed in HTTP if it can’t load HTTPS without breaking the site.

  • Disabled = Don’t upgrade HTTPS connections would disable the protection completely. Sites can load in HTTP without attempting to upgrade to HTTPS.

2 Likes

@Saoiray whoops you’re absolutely right — definitely read “Fingerprinting” for some reason and didn’t check twice. Thank you for the correction and great answer as well.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.