All Documents
Current Document

Content is empty

If you don't find the content you expect, please try another search term

Documentation

How do I deal with HTTP content errors on the webpage after installing an SSL certificate?

Last updated:2024-03-15 16:28:22

The name on the security certificate is invalid or does not match the name of the site If you access a website by using its IP address, the website returns The name on the security certificate is invalid or does not match the name of the site message. The reason is that the certificate is bound with the domain name of the website. When you access the website, the website checks whether the domain name declared on the certificate is the domain name of the website itself. To resolve the problem, use the domain name of the website to access the website.

This page contains both secure and nonsecure items If you access a webpage that contains both HTTP resources and HTTPS resources, the website returns This page contains both secure and nonsecure items message. To resolve the problem, you must adjust the webpage contents. If the website contains flash resources, download the Adobe Flash Player control installation package to the server and change the control installation package address to the path of the package on the server. Use relative paths as webpage addresses if possible. Using relative paths allows both HTTP access and HTTPS access. If you need to use the absolute path of a webpage and the webpage requires using HTTPS for access, use the fully qualified path as the URL.

A webpage contains HTTP resources in a variety of situations, for example:

  • The webpage contains links to non-HTTPS resources on other websites, for example, http://.../img/baidu_logo.gif. To resolve the problem, download the non-HTTPS resources from the websites to the server and change the resource paths to the paths on the server. Alternatively, you can obtain the HTTPS URLs of the websites, for example, https://.../img/baidu_logo.gif.

  • The webpage does not contain links to non-HTTPS resources on other websites but uses its fully qualified path as the URL, for example, http://.../image/image1024.gif. To resolve the problem, use the relative paths (for example, < img src="image/image1024.gif">) or use the fully qualified HTTPS path (for example, URL < img src=https://.../image/image1024.gif>).

The following are some best practices:

  • If a webpage contains links to pictures or .js scripts, use relative paths if possible. For example, use demo/image.jpg instead of http://.../demo/image.jpg.

  • If a webpage contains links to flash resources, download the Adobe control to the server and modify the control path. You can also choose to delete the control installation code.

  • If a webpage contains links to non-HTTPS resources on other websites, download the non-HTTPS resources from the websites to the server and change the resource paths to the paths on the server. If a webpage contains links to HTTPS resources on other websites, you can access the links without taking any measure.

On this page
Pure ModeNormal Mode

Pure Mode

Click to preview the document content in full screen
Feedback