https:// connecting on cplusplus.com
I can't connect this web site with secure http
I get the error on firefox and others
this error are SSL_ERROR_RX_RECORD_TOO_LONG on firefox
(This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.) on ms edge
else?
does not having the certificate this website
I get the error on firefox and others
this error are SSL_ERROR_RX_RECORD_TOO_LONG on firefox
(This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.) on ms edge
else?
does not having the certificate this website
Last edited on
It's unfortunate that this site does not support SSL, however, there's no secret information on this web-site - nothing to protect.
Use a unique password, as you should be doing already, and the issue shouldn't be of much concern.
Use a unique password, as you should be doing already, and the issue shouldn't be of much concern.
if the openssl is free, it is not a problem! Deceptive sites even have ssl connection! I came across! When looking!
it's up to your desire!
it looks at your wish
it's up to your desire!
it looks at your wish
No, it takes some non-trivial effort to convert a site from http: to https:, and this site is not going to get that treatment. It is old as-is. A near-complete rewrite is in order, and that isn’t going to happen.
Why does it bother you so much? Is your modern browser producing FUD about the http: connection?
Why does it bother you so much? Is your modern browser producing FUD about the http: connection?
> No, it takes some non-trivial effort to convert a site from http: to https:,
What makes you say that? Part of my job is to help bring old and new sites from HTTP to HTTPS. It's fairly trivial these days, especially with Nginx. This server uses apache, but it is pretty simple with that as well.
edit: unless of course you're using extremely outdated, unsupported software, but even then, it would have to be really old to make going to https a pain.
What makes you say that? Part of my job is to help bring old and new sites from HTTP to HTTPS. It's fairly trivial these days, especially with Nginx. This server uses apache, but it is pretty simple with that as well.
edit: unless of course you're using extremely outdated, unsupported software, but even then, it would have to be really old to make going to https a pain.
Last edited on
Bad choice of words on my part. What I meant was that there is more to it than just changing http: to https:, and not all the changes are really obvious unless you know what you are doing.
For reference, I barely know anything about it outside of messing with my own domain.
For reference, I barely know anything about it outside of messing with my own domain.
Whether the conversion is easy or hard, simple or complex, it is all up to the site owner.
If they want to pay for the conversion, time and money, it'll happen.
If they want to pay for the conversion, time and money, it'll happen.
Topic archived. No new replies allowed.