Web security
Web security
When I get am email letting me know someone has replied to my post, the URL provided in the email uses HTTP.
My security software blocks me from using that URL, it wants HTTPS.
I have to copy the URL and edit it to add the S to HTTP.
Can you fix this?
Web security is a big deal these days.
My security software blocks me from using that URL, it wants HTTPS.
I have to copy the URL and edit it to add the S to HTTP.
Can you fix this?
Web security is a big deal these days.
- crfriend
- Master Barista
- Posts: 15151
- Joined: Fri Nov 19, 2004 9:52 pm
- Location: New England (U.S.)
- Contact:
Re: Web security
I just made a minor tweak to the back-end configuration to change the default protocol to https:// instead of http:// and let's see what happens.
If the above fails, I can force the setting, but that may break folks with older browsers who don't have the CA "chain of trust" required for our CA (Certificate Authority -- the ones who sign our https:// key). I know of at least one user (Hi, Fred!) that has this problem and I'm not interested in breaking current functionality for anyone when the issue is trivially dealt with at the client end by inserting an "s" into the method field of the URI (Universal Record Identifier).
If the above fails, I can force the setting, but that may break folks with older browsers who don't have the CA "chain of trust" required for our CA (Certificate Authority -- the ones who sign our https:// key). I know of at least one user (Hi, Fred!) that has this problem and I'm not interested in breaking current functionality for anyone when the issue is trivially dealt with at the client end by inserting an "s" into the method field of the URI (Universal Record Identifier).
Retrocomputing -- It's not just a job, it's an adventure!
- Fred in Skirts
- Member Extraordinaire
- Posts: 4162
- Joined: Mon Mar 14, 2016 6:48 pm
- Location: Southeast Corner of Aiken County, SC USA
Re: Web security
Hi Carl!crfriend wrote:I just made a minor tweak to the back-end configuration to change the default protocol to https:// instead of http:// and let's see what happens.
If the above fails, I can force the setting, but that may break folks with older browsers who don't have the CA "chain of trust" required for our CA (Certificate Authority -- the ones who sign our https:// key). I know of at least one user (Hi, Fred!) that has this problem and I'm not interested in breaking current functionality for anyone when the issue is trivially dealt with at the client end by inserting an "s" into the method field of the URI (Universal Record Identifier).
"It is better to be hated for what you are than be loved for what you are not" Andre Gide: 1869 - 1951
Always be yourself because the people that matter don’t mind and the ones that mind don’t matter.
Always be yourself because the people that matter don’t mind and the ones that mind don’t matter.

-
- Member Extraordinaire
- Posts: 1474
- Joined: Thu Apr 05, 2018 3:17 pm
Re: Web security
Hi Carl... never asked for this service....I check board index weeladdie
- crfriend
- Master Barista
- Posts: 15151
- Joined: Fri Nov 19, 2004 9:52 pm
- Location: New England (U.S.)
- Contact:
Re: Web security
Hopefully it is transparent. It should be if you're running a modern browser with an up-to-date CA chain.weeladdie18 wrote:Hi Carl... never asked for this service....I check board index weeladdie
Is there a problem?
Retrocomputing -- It's not just a job, it's an adventure!