Hello Hesam,
Thank you for the link. I've read this page before and it is actually what I used as a guide to set up Pound. However I don't see anywhere on the page that describes how to set up transparent error forwarding. I only see information about setting up custom static error pages using the ErrXXX directives. These directives are not what I'm looking for. I want Pound to forward error messages generated by backend servers to clients/browsers, but Pound simply substitutes it's own error message: "An internal server error occurred" Amal From: hesam mohamadian [mailto:[email protected]] Sent: Sunday, June 05, 2011 12:02 AM To: [email protected] Subject: Re: [Pound Mailing List] passing server http errors through Hi , Amal Please see this link you can get your answer there https://calomel.org/pound.html with a best wishes , Hesam On Thu, Jun 2, 2011 at 8:31 PM, Amal Graafstra <[email protected]> wrote: Hi all, I've been using pound as a reverse proxy for a little while now, and I love it. It allows me to host a plethora of web services across a diverse server landscape (windows, *nix, micro, etc.) while conserving public IP address space. My question though is this; is it possible to allow pound to pass-through HTTP error messages from the server to the client? For example, a backend server hits an error and dumps out the details that caused the error, however those details are replaced by pound with a simple "An internal server error occurred". I don't want to use Err500 to serve up a static file, I'd like to be able to pass the actual backend error to the browser through pound. Is that possible? Thanks, Amal -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
