Contents
Why does my browser still show my site as insecure?
A common issue after adding an SSL certificate is that your browser still shows your site as insecure. This most often happens because there are links on your page that still point to HTTP instead of HTTPS. For example, look at the following code to link an image.
Can a https redirect be performed at a server level?
Performing an HTTPS redirect at server level is usually the preferred option. In this case, the server where the SSL certificate is installed receives the encrypted HTTP request and returns an encrypted HTTP redirect response according to some configuration rules, without contacting the application server or executing the application code.
Why is my website still insecure after SSL certificate?
A common issue after adding an SSL certificate is that your browser still shows your site as insecure. This most often happens because there are links on your page that still point to HTTP instead of HTTPS. For example, look at the following code to link an image.
What happens when a redirect is sent to a server?
At that point, the client will send the HTTP request to the server, and the server will finally respond with the HTTP response containing the redirect. A redirect is nothing more than an HTTP response with a 301 (sometimes 302 or 307) status code. Once again, the order is: The client and the server agree to exchange the SSL certificate information.
Does an internal site need to have HTTPS security?
The question is in the title. Does an internal site need to have https security? For example we have an internal site that handles our client’s license keys — do we need for that to be secure since it is on our internal network?
What to do when your website says not secure?
If a site you frequently use is displaying the “Not Secure” warning, you should contact them and ask them to start supporting HTTPS. You can also try manually replacing HTTP with HTTPS in the URL, as some sites may have partial support for HTTPS but don’t offer it by default.