Hi I'm using pound v2.1.
I am finding that some of the keywords people have suggest don't work with pound 2.1 (e.g ExtendedHTTP & HTTPSHeaders )
I did a bit more investigation, I downloaded a Mozilla plugin called LiveHTTPHeaders which allows you to see what UPL's you browser is loading. It appears as if Outllook is somehow redirecting the browser to a http:// address rather than a https one. I thought that pound would deal with this but I suspect it may be microsoft OWA doing something "non standard". The page that gets loaded finally has https:// in the address bar, but some the components of the frames that make it up the page seem to get loaded through http. See below
As my Reverse proxy is not listening for http this is where it fails. In the pound.cfg that was posted by Frode (thanks!) it is listening for both http & https. If I add a http proxy config to my current pound.cfg
I can now sort of get it to work, but I still get the message about secure and non secure content and I have to login twice (with IE6).
If we can get to the bottom of how the "http" is leaking through the reverse proxy it would be a done deal. Any Ideas?
On 9/7/06, dirk dekker <firstname.lastname@example.org> wrote:
Hi, I'm not an expert in pound and trying to work with it :)
What version of pound do you have installed ( and on what OS) ?
Van: Frode Egeland [mailto:email@example.com]
Verzonden: donderdag 7 september 2006 11:29
Onderwerp: Re: [Pound Mailing List] Does anyone have Oulook Web Access
3. My browser starts to load the site (skeleton frames are set up in my
> browser) but a box pops up saying this site contains secure and
> nonsecure items (which is weird) and do I want to display the
> nonsecure ones. I click yes 4. Both of the frames in my browser
> display "The Page cannot be displayed"
I'm just working with a test setup, and I had almost exactly the same issue.
Now it works, and here's my config:
-- start of /etc/pond/pound.cfg --
HTTPSHeaders 0 "Front-End-Https: on"
ListenHTTPS *,443 /etc/pound/pound.pem
-- end of file --
It seems to work nicely, but I'm sure some experts on this list will see
something that's gonna bite me later (please let me know!!)..
To unsubscribe send an email with subject 'unsubscribe' to firstname.lastname@example.org.
Please contact email@example.com
To unsubscribe send an email with subject 'unsubscribe' to
Please contact firstname.lastname@example.org for questions.