Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

I am using Apache as a proxy frontend for a Java web application, which is deployed on WebSphere. The web application is using custom status codes (55x) to signal specific errors to the clients. When accessing the web application directly through the WebSphere HTTP listener, everything works as expected, but when these requests are proxied through an Apache load balancer, the status codes are modified by Apache and replaced with a generic 500 error code (internal server error).

In Apache's access.log, the correct status code is logged:

<IP> - - [11/Nov/2011:17:24:53 +0100] "POST <URL> HTTP/1.1" 551 36

But the actual response received by the client starts like this (logged with tcpdump):

HTTP/1.1 500 Internal Server Error

Followed by the real status code in the response content:

... Error 551: Berichteter Fehler: 551 ...

Is there an obvious reason for this behaviour or does someone have a suggestion on how to modify the Apache configuration to forward the "real" status code instead of 500?

share|improve this question

migrated from Nov 13 '11 at 6:02

This question came from our site for professional and enthusiast programmers.

sticky bit is active? – Anders Nov 11 '11 at 16:36

Your Answer


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

Browse other questions tagged or ask your own question.