by musonius » Sat Jun 15, 2019 10:19 pm
If I trust trusteddomain.com for HTTP, it will also be trusted for HTTPS, which is exactly what I expect. There is the padlock to switch between trusting a domain for HTTPS only (green padlock) or for both protocols (red padlock).
But if I set untrusteddomain.com to UNTRUSTED for HTTPS, the domain untrusteddomain.com will still be set to DEFAULT for HTTP. That is, I have to set a domain to UNTRUSTED for HTTP, if I want the setting to be applied for both protocols. Unfortunately, there is no padlock to do that, which is what I prefer to do, if HTTPS is the current protocol.
Does that work as intended? If it does, what's the reason? I'd expect the UNTRUSTED preset to work the other way round than the TRUSTED preset. If I don't trust untrusteddomain.com for the protocol HTTPS, I won't trust it for HTTP either.
If I trust [i]trusteddomain.com[/i] for HTTP, it will also be trusted for HTTPS, which is exactly what I expect. There is the padlock to switch between trusting a domain for HTTPS only (green padlock) or for both protocols (red padlock).
But if I set [i]untrusteddomain.com[/i] to UNTRUSTED for HTTPS, the domain [i]untrusteddomain.com[/i] will still be set to DEFAULT for HTTP. That is, I have to set a domain to UNTRUSTED for HTTP, if I want the setting to be applied for both protocols. Unfortunately, there is no padlock to do that, which is what I prefer to do, if HTTPS is the current protocol.
Does that work as intended? If it does, what's the reason? I'd expect the UNTRUSTED preset to work the other way round than the TRUSTED preset. If I don't trust [i]untrusteddomain.com[/i] for the protocol HTTPS, I won't trust it for HTTP either.