Shamunda wrote:
I'm not sure what you mean by that, but then again being new to this
stuff I may have it completely wrong.
I thought the way in was the only way out?
Example.
User types HTTPS://URL -----> ssl pound server ------> Backend HTTP
server
and the return path was:
User Receive HTTPS://URL <----- ssl pound server <------ Backend HTTP
Server
Right, that's how almost all reverse proxies work, pound included. Its
only different if you're using DSR (direct server return), which you're
not if you're using pound. :)
Could someone post a configuration they have (stripping out all the
address info of course), that has POUND as the front end SSL layer.
Your pound config looked fine in previous postings. My point is, your
backend server is fully capable of issuing a redirect to tell the
browser to switch to http. Pound happily passes these onto the user,
and you see the change in the address bar of your browser. I'd
recommend that you sniff the traffic between pound and your backend
server and see what comes across the wire - I expect you'll see a HTTP
302 code with a location that's not using https.
Alternative look at your application running on your backend and check
if it requires SSL. If possible, disable that, and enforce SSL with pound.
--
Dave Steinberg
http://www.geekisp.com/
http://www.steinbergcomputing.com/
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
