Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Apache is acting as a reverse proxy in my setup. The application server running on port 8081 requires a valid Authorization header. The header is set by the client application. Apache seems to remove this header. It does not reach the server on port 8081.


    <Proxy *>
            Order deny,allow
            Allow from all

    SSLEngine On
    SSLCertificateFile /etc/apache2/ssl/apache.pem

    ProxyPreserveHost On
    ProxyRequests Off
    ProxyPass /
    ProxyPassReverse /

To verify the server on port 8081 is working correctly, I added RequestHeader set Authorization "Basic XZY" to that configuration. In this case, the header is processed correctly by the server on port 8081.

I also connected to the server on port 8081 directly from the client to make sure the client is really setting the correct header. That also worked well.

share|improve this question

From the mod_proxy_http docs:


If the proxy requires authentication, it will read and consume the proxy authentication credentials sent by the client. With proxy-chain-auth it will also forward the credentials to the next proxy in the chain. This may be necessary if you have a chain of proxies that share authentication information. Security Warning: Do not set this unless you know you need it, as it forwards sensitive information!

Is this what you are looking for?

share|improve this answer
up vote 0 down vote accepted

It turned out the the reason was a buggy client implementation.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.