{"id":2264,"date":"2026-10-13T05:44:34","date_gmt":"2026-10-12T21:44:34","guid":{"rendered":"https:\/\/www.gxcom.net\/"},"modified":"2026-10-13T05:44:34","modified_gmt":"2026-10-12T21:44:34","slug":"http-to-https-redirect-guide","status":"publish","type":"post","link":"https:\/\/www.gxcom.net\/zh\/http-to-https-redirect-guide\/","title":{"rendered":"HTTP \u5230 HTTPS \u91cd\u5b9a\u5411\u6307\u5357\uff1a\u89e3\u51b3\u91cd\u5b9a\u5411\u5faa\u73af\u548c\u6df7\u5408\u5185\u5bb9\u95ee\u9898"},"content":{"rendered":"

Switching from HTTP to HTTPS is essential for protecting website connections, but an incorrect redirect can cause ERR_TOO_MANY_REDIRECTS<\/strong>, broken pages, or mixed content warnings.<\/p>\n

This HTTP to HTTPS redirect guide<\/strong> explains how to configure permanent redirects in Apache and Nginx, troubleshoot WordPress redirect loops, and fix insecure resources after enabling SSL.<\/p>\n

What Is an HTTP to HTTPS Redirect?<\/h2>\n

An HTTP to HTTPS redirect sends visitors from an unencrypted URL to its secure HTTPS equivalent.<\/p>\n

For example:<\/p>\n

http:\/\/example.com\/page\/\r\n\u2192 https:\/\/example.com\/page\/<\/code><\/pre>\n
A permanent 301 redirect<\/strong> is commonly appropriate after completing an HTTPS migration. It tells browsers and search engines that the resource has moved permanently.<\/p>\n
Quick answer:<\/strong> Install a valid TLS certificate, configure one consistent redirect rule, update internal URLs, and verify that pages load without insecure resources or redirect loops.<\/p>\n
\"HTTP<\/p>\n
1. Check Your SSL Certificate First<\/h2>\n
Before configuring redirects, confirm that HTTPS works directly:<\/p>\n
https:\/\/example.com<\/code><\/pre>\n
Check that the certificate is valid, matches the hostname, and includes any required www or non-www variant.<\/p>\n
If HTTPS fails before redirection, fix the certificate or server configuration first.<\/p>\n
For certificate renewal problems, see our Let's Encrypt SSL Auto-Renewal Troubleshooting Guide<\/a>.<\/p>\n
2. Configure HTTP to HTTPS Redirects in Apache<\/h2>\n
For Apache servers using .htaccess<\/code> with mod_rewrite<\/code> enabled, a common rule is:<\/p>\n
RewriteEngine On\r\nRewriteCond %{HTTPS} !=on\r\nRewriteRule ^ https:\/\/%{HTTP_HOST}%{REQUEST_URI} [R=301,L]<\/code><\/pre>\n
This redirects HTTP requests to the corresponding HTTPS URL.<\/p>\n
However, behind a reverse proxy or CDN, Apache may receive HTTP traffic even when the visitor connects using HTTPS. In that situation, a basic HTTPS condition can create a loop.<\/p>\n
Use the proxy-aware configuration recommended by your hosting platform instead of adding conflicting rules.<\/p>\n
3. Configure HTTP to HTTPS Redirects in Nginx<\/h2>\n
On Nginx, HTTP redirection is usually configured in the port 80 server block:<\/p>\n
server {\r\n    listen 80;\r\n    server_name example.com www.example.com;\r\n    return 301 https:\/\/$host$request_uri;\r\n}<\/code><\/pre>\n
Your HTTPS server block must separately handle TLS connections with the appropriate certificate.<\/p>\n
After editing the configuration, validate it:<\/p>\n
sudo nginx -t<\/code><\/pre>\n
If validation succeeds, reload Nginx:<\/p>\n
sudo systemctl reload nginx<\/code><\/pre>\n
Avoid adding the same redirect independently at the CDN, load balancer, web server, and application layers without understanding how they interact.<\/p>\n
4. Fix ERR_TOO_MANY_REDIRECTS<\/h2>\n
A redirect loop occurs when two or more rules repeatedly send the browser between URLs.<\/p>\n
Common causes include:<\/p>\n