Has anyone seen an HTTP 500 error when HTTPS traffic going through Pound Proxy forwards to an HTTP page?

Posted by scientastic on Server Fault See other posts from Server Fault or by scientastic
Published on 2010-12-03T21:50:43Z Indexed on 2011/03/05 7:26 UTC
Read the original article Hit count: 143

Filed under:
|
|
|

We have Varnish as our load balancer and reverse proxy cache for normal HTTP traffic. For HTTPS traffic, we use Pound proxy to unwrap the SSL and forward to Varnish, which then forwards to the back-end servers. This is used for our "checkout" process to encrypt credit card info in transition. However, on the last stage of checkout, users are always getting an HTTP 500 (Internal Server) error. It doesn't seem to be due to our back-end app server, by all tests I've tried. Does anyone know anything about how that transition works-- the transition back from HTTPS to HTTP and the interaction between Pound and Varnish-- and why it might cause 500 errors?

© Server Fault or respective owner

Related posts about https

Related posts about reverse-proxy