Apache httpd：当存在Location头时修改返回状态码

Absolutely! You can fix this mismatch between the Location header and 200 status code using Apache's built-in modules—here are two reliable, straightforward approaches tailored for your reverse proxy setup:

Option 1: Use mod_headers (Recommended for Simplicity) #

This module is purpose-built for manipulating response headers and status codes, making it the cleanest solution for your use case.

Steps: #

1. Enable the module (if not already active):

   • For Debian/Ubuntu systems:

     sudo a2enmod headers
     

   • For RHEL/CentOS systems:
     Uncomment this line in your httpd.conf or conf.modules.d/00-base.conf:

     LoadModule headers_module modules/mod_headers.so
     

2. Add the rule to your Apache config (place this inside your reverse proxy's <VirtualHost> block, or a <Location> block targeting your app's specific path):

   # Set status code to 302 ONLY when response has a Location header AND status is 200
   Header always set Status "302 Found" "expr=%{RESPONSE_LOCATION} =~ /.+/ && %{RESPONSE_STATUS} == 200"
   

   • The always flag ensures the rule applies across all response phases (critical for reverse proxy traffic)
   • The expr condition checks two key things: that the Location header is non-empty, and the original status code is 200

Option 2: Use mod_rewrite (If You Already Use Rewrite Rules) #

If you're already leveraging mod_rewrite for other routing or proxy tasks, this approach integrates seamlessly:

Steps: #

1. Enable the module (if not active):

   • Debian/Ubuntu:

     sudo a2enmod rewrite
     

   • RHEL/CentOS:
     Uncomment this line in your config:

     LoadModule rewrite_module modules/mod_rewrite.so
     

2. Add the rewrite rules to your proxy config block:

   RewriteEngine On
   # Only target responses with 200 status code
   RewriteCond %{RESPONSE_STATUS} ^200$
   # Only target responses that have a non-empty Location header
   RewriteCond %{RESPONSE_LOCATION} .+
   # Override status code to 302; L = stop processing further rules
   RewriteRule ^ - [R=302,L]
   

Critical Post-Setup Steps #

• Test your config to catch syntax errors before restarting:

  # Debian/Ubuntu
  sudo apache2ctl configtest
  # RHEL/CentOS
  sudo httpd -t
  

• Restart Apache to apply changes:

  # Debian/Ubuntu
  sudo systemctl restart apache2
  # RHEL/CentOS
  sudo systemctl restart httpd
  

Either approach will force the browser to respect the Location header by switching the status code to 302 exactly when your backend app returns a 200 with a redirect URL.

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