Dear pound list,

I have a weird scenario with my pound installation.
I have a new application behind my load balancer that uses a combination of
Webserver and Tomcat. The application talks to the clients and
implemented some custom error codes (in the 4xx range) to communicate update
requirements and incompatibilities to the client.
I can see at the Webserver, that the tomcat is delivering a 432 status to the
client, however, after the pound the http message is a 500.
The client does not know what to do with a 500 status and prints an error.
Is there a way to teach pound the 4xx errors?

Thanks, Peter 
--
DI Peter Burgstaller
-----------------------------------
Head of Hosted Services

SKIDATA AG
Untersbergstraße 40
A-5083 Grödig, Salzburg
[p] +43 (0) 6246 888-4155
[f] +43 (0) 6246 888-7
[e] peter.burgstaller(at)skidata.com
[w] http://www.skidata.com

I don't see anything in the code that would validate 4xx codes. If the backend
passes it then pound should pass it along.

However, if pound is creating a 500 error, it would be in the log. (i.e. e500
headers: out of memory, or e500 can't read header)  Do you see any messages in
the log that correspond with the 500 error?

If not, maybe your webserver is turning it into a 500 error?

Joe
[...]