but this post utility adds the additional "//http:" for some reasonAh, sorry. I missed your edit. Sorry about that. Next time just paste the url as text (not a link) or use code tags.
How do I turn redirection on?
is that a lazarus or browser thing?It is a TFPHTTPClient class thing :)
http isn't valid for ages.
That is a bit misleading. There are plenty of sites that are still using HTTP and not HTTPS. Just because HTTPS is popular doesn't necessarily mean that every site needs/uses it.You are correct Remy. It is misleading because you are right: there still exists websites that accept http. My apologies.
http isn't valid for ages. The second url, is invalid by deifnitionWrong, still valid.
Wrong, still valid.No idea in what universe the url ...
http://httP://www.yahoo.com
.. is valid, but hey if it does in yours then I am happy for you (forum software seems to agree with you) ;DThat is a bit misleading. There are plenty of sites that are still using HTTP and not HTTPS. Just because HTTPS is popular doesn't necessarily mean that every site needs/uses it.You are correct Remy. It is misleading because you are right: there still exists websites that accept http. My apologies.
However, major browser builders have mandated that we are not allowed to access those anymore. As a result the number of websites that are accessible by http seem to decline as a result.
I hope that is not the case, I use http//.. to connection to hardware using the default browser in the pc. That would be a tragic event if that stopped.Unfortunately it is. And indeed it is a PITA as I am also unable to access some devices on my local network in that way. On some of my systems I have to resort to either a custom solution or use an older browser that still supports http. Not every (recent) browser allows to override the behaviour of forcing https. It the same annoying behaviour as that some browsers removed ftp support.
Unfortunately it is. And indeed it is a PITA as I am also unable to access some devices on my local network in that way. On some of my systems I have to resort to either a custom solution or use an older browser that still supports http. Not every (recent) browser allows to override the behaviour of forcing https.
However, major browser builders have mandated that we are not allowed to access those anymore. As a result the number of websites that are accessible by http seem to decline as a result.
Unfortunately it is.Fortunately it is not. Come on Ron, admit you are wrong.
Since the http:// sites are 100% static, there is no need for https.Except that an attacker can impersonate your website. There are a whole host of attacks that are possible. E.g. an attacker can inject javascript into the website to mine cryptocurrencies with the users browser while they visit your website or more overtly could embedd advertisements to gain money from the people visiting your website. Or an attacker could use the trust the user has into your website and trick people with scams, e.g. advocating for some dubious services or something. A bit more malicious they could provide downloads which contain malware or link to malicious websites etc.
.....
Static or not, HTTPS should always be used unless in very specific circumstances (e.g. on calls to localhost, or extremely small local networks), especially as Let's Encrypt makes it completely free