javascript - How to deal with link problems after the website is changed to https?

The website did not have the https protocol enabled before.
All links are absolute links, almost no relative links.
The current situation is that after turning on https, all absolute links and images become invalid. Since the website has many pages, is there any way to change the links in batches?

Reply content:

The website did not have the https protocol enabled before.
All links are absolute links, almost no relative links.
The current situation is that after turning on https, all absolute links and images become invalid. Since the website has many pages, is there any way to change the links in batches?

Directly use the WEB server for permanent redirection, NGINX as an example

<code>server{
    listen 80;
    server_name test.com;
    #告诉浏览器2年有效期内只准用 https 访问
    add_header Strict-Transport-Security "max-age=63072000; includeSubdomains; preload";
    #永久重定向到 https 站点
    return 301 https://$server_name$request_uri;
}</code>

If you really don’t have permission to set the configuration, then write a script to replace it in batches, or download the code to the local, and then use IDE to replace it in batches.
Please make a backup before modifying
Scripts with similar functions

<code>sed -i "s/http:\/\/www.old.com/https:\/\/www.old.com/g" `grep http://www.old.com -rl /path/to/project`</code>

https://imququ.com/post/sth-a...

In the process of migrating a long-established website to HTTPS, the workload is often very huge. Especially in the step of replacing all resources with HTTPS, it is easy to make omissions. Even if all the code confirms that there are no problems, it is possible that there are still HTTP links in some of the fields read from the database.
With the upgrade-insecure-requests CSP directive, the browser can help with this conversion. After enabling this policy, there are two changes:
All HTTP resources on the page will be replaced with HTTPS addresses before making requests;
All on-site links on the page will be replaced with HTTPS addresses before jumping after being clicked;
With all other CSP rules Similarly, there are two ways to enable this command. Please refer to the previous section for the specific format. It should be noted that upgrade-insecure-requests only replaces the protocol part, so it is only applicable to scenarios where the HTTP/HTTPS domain name and path are exactly the same.

General compilation software has a one-click replacement function.

Rewriting the url should work

Your website won’t be a fully static page, right? If not, then change the template. Also, the URL is usually generated through a specified function. Just change the function. If the image path is in the database, just replace it in batches. For the page image file, change the template. That’ll be fine

Now you know the importance of packaging

403 jump;