Express在Serverless/Lambda容器中重定向功能失效问题

I’ve hit this exact snag before when deploying Express apps to Serverless/Lambda setups—let’s break down why it breaks and how to fix it:

Why It Works Locally But Fails on Serverless #

When running locally, Express handles requests directly. Calling res.redirect('/api/newroute') uses the current request’s host (localhost) and full path context to build the correct redirect URL (http://localhost/api/newroute).

But in Serverless/Lambda environments (like AWS Lambda + API Gateway), your Express app sits behind a proxy. This proxy often modifies request headers, path details, or the host value that Express sees. As a result, the relative path in res.redirect() might resolve to an incorrect URL—for example, pointing to the API Gateway’s domain instead of your app’s, or missing the /api prefix entirely.

Solutions to Fix the Redirect #

1. Use Absolute URLs Instead of Relative Paths #

The most reliable fix is to build a full absolute URL for the redirect, accounting for proxy headers that carry the original client’s request details:

app.get('/api/route2', (req, res) => {
  // Grab protocol and host from proxy headers (fallback to local values)
  const protocol = req.headers['x-forwarded-proto'] || req.protocol;
  const host = req.headers['x-forwarded-host'] || req.get('host');
  
  const redirectUrl = `${protocol}://${host}/api/newroute`;
  res.redirect(redirectUrl);
});

Most Serverless proxies (like API Gateway) add x-forwarded-proto and x-forwarded-host headers with the original client’s protocol (http/https) and host. Falling back to req.protocol and req.get('host') ensures this still works seamlessly in your local dev environment.

2. Configure Express to Trust the Proxy #

Tell Express to trust the proxy server so it correctly parses the original request details. Add this line at the top of your Express app:

app.set('trust proxy', true);

This makes Express use x-forwarded-* headers by default for properties like req.protocol and req.hostname. With this set, you might even get relative paths working again, but absolute URLs remain more reliable for complex Serverless setups.

3. Verify Your Serverless Path Mapping #

Double-check how your Serverless provider routes requests to your Lambda function. For example, in AWS API Gateway:

• Ensure your API Gateway resource maps to /api/* (not just /*) so the full /api/route2 path is passed to your Express app.
• If using a custom domain, confirm the base path mapping is set to /api to match your local setup.

If the path sent to Lambda is missing the /api prefix, your Express route won’t match, and the redirect logic won’t fire as expected.

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