Node环境下HTTP转HTTPS重定向次数过多（AWS服务器异常）求助

Hey Connor, let's break down why you're hitting that "URL redirected too many times" error on AWS when your HTTP-to-HTTPS redirect works perfectly locally. Here are the most common causes and fixes to get this sorted:

This is the #1 culprit for this issue on AWS. Most often, your ALB/NLB or CloudFront handles SSL termination at the edge—meaning it accepts HTTPS traffic from users, then forwards HTTP traffic to your backend server. If your backend is still forcing a redirect from HTTP to HTTPS, you get an infinite loop:

User → HTTPS to LB → LB sends HTTP to backend → backend redirects to HTTPS → LB sends HTTP again... repeat forever.

Fix it:

• Update your backend config (Nginx/Apache) to only redirect when the original request wasn't HTTPS, using the X-Forwarded-Proto header that AWS proxies send:
  • Nginx example:

    server {
        listen 80;
        # Only redirect if the original request was HTTP
        if ($http_x_forwarded_proto = 'http') {
            return 301 https://$host$request_uri;
        }
        # Rest of your server config
    }
    

  • Apache example:

    RewriteEngine On
    # Check if the original protocol wasn't HTTPS
    RewriteCond %{HTTP:X-Forwarded-Proto} !https
    RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L]
    

• Double-check your AWS proxy (ALB/CloudFront) is configured to send the X-Forwarded-Proto header—ALBs do this by default, but it's worth confirming.

If you're using CloudFront as your CDN, misconfigured cache rules can cause redirect loops:

• If you set your backend to redirect HTTP to HTTPS and set CloudFront's viewer protocol policy to redirect HTTP to HTTPS, you might get conflicting redirects.
• Or, old redirect rules might be cached in CloudFront, causing stale behavior.

Fix it:

• In your CloudFront distribution's cache behavior, set the Viewer Protocol Policy to Redirect HTTP to HTTPS—this lets CloudFront handle the redirect at the edge, so your backend doesn't need to.
• If you already have backend redirects, make sure they don't conflict. And invalidate CloudFront cache to clear any stale rules: run aws cloudfront create-invalidation --distribution-id YOUR_DIST_ID --paths "/*" or use the AWS console.

A misconfigured SSL certificate on AWS can break HTTPS handshake, leading browsers to fall back to HTTP, which then gets redirected to HTTPS—creating a loop.

Fix it:

• Check your AWS Certificate Manager (ACM) certificate: ensure it's marked "Issued" and correctly attached to your ALB/CloudFront distribution.
• Verify the certificate covers your exact domain (e.g., www.yourdomain.com or a wildcard *.yourdomain.com). Mismatched domains can cause SSL errors that trigger redirect loops.

If AWS security groups or network ACLs (NACLs) block port 443 (HTTPS) traffic, browsers can't establish an HTTPS connection, so they retry HTTP—only to be redirected back to HTTPS, creating a loop.

Fix it:

• For security groups: Add an inbound rule allowing port 443 from 0.0.0.0/0 (or your specific IP range for testing) and an outbound rule allowing port 443 to 0.0.0.0/0.
• For NACLs: Ensure both inbound and outbound rules allow traffic on port 443 (HTTPS).

Locally, you're probably accessing your server directly over HTTPS (no proxy), so your simple "HTTP → HTTPS" redirect works. On AWS, the proxy layer changes the traffic flow, making your local rule incompatible.

Fix it:

• Adopt the X-Forwarded-Proto-based redirect rule mentioned earlier for your local environment too. This way, your config works both locally and on AWS without changes.

Start with checking the load balancer/CloudFront SSL termination and X-Forwarded-Proto configuration—that's almost always the root cause here.

内容的提问来源于stack exchange，提问作者connorvo