Its 2017 for Gods sake, why is our http://www website showing up as not secure??? Who cares, why are you slandering us and blocking access?
http:// websites are blocked for not having security certificate.
선택된 해결법
HTTP websites aren't blocked in any way. They are merely flagged especially in case there is a login form to an insecure URL, but you should still be able to visit such a website without any problems.
The page links you posted have a meta refresh tag that redirects to a server that doesn't have a certificate installed. view-source:http://shirtsquirts.com/
<meta HTTP-EQUIV="REFRESH" content="5; url=https://www.securepaynet.net/default.aspx?prog%5Fid=inmarvs"> <link rel="stylesheet" href="style.css" type="text/css" media="screen" />
The HTTP version redirects as well and ends up with domainspricedright.
- http://www.securepaynet.net/default.aspx?prog%5Fid=inmarvs
- https://www.secureserver.net/?prog_id=domainspricedright
- https://www.domainspricedright.com/
So in this case there is a lot wrong that needs to be fixed.
문맥에 따라 이 답변을 읽어주세요 👍 0모든 댓글 (4)
선택된 해결법
HTTP websites aren't blocked in any way. They are merely flagged especially in case there is a login form to an insecure URL, but you should still be able to visit such a website without any problems.
The page links you posted have a meta refresh tag that redirects to a server that doesn't have a certificate installed. view-source:http://shirtsquirts.com/
<meta HTTP-EQUIV="REFRESH" content="5; url=https://www.securepaynet.net/default.aspx?prog%5Fid=inmarvs"> <link rel="stylesheet" href="style.css" type="text/css" media="screen" />
The HTTP version redirects as well and ends up with domainspricedright.
- http://www.securepaynet.net/default.aspx?prog%5Fid=inmarvs
- https://www.secureserver.net/?prog_id=domainspricedright
- https://www.domainspricedright.com/
So in this case there is a lot wrong that needs to be fixed.
OMG I am so sorry. Long day(s). Just removed the redirect I had forgotten about and everything is normal. Thank You for your time. :-)
You're welcome and thanks for reporting that you fixed this.