In older versions of pound, it would send the request to the backend as
www.website.com:443, so some apps would check for that and perform the
rewrite to https if it wasn't 443.  Now, even though you're coming in on
443, pound now sends the request to the backend either blank
(www.website.com) or as (www.website.com:80), I don't remember which
way.  This got us too, since the behavior changed between 1.x and 2.x.

Now we use a custom header in the pound config for SSL (front-end-https:
on) and check for that.

--Alfonso

-----Original Message-----
From: william pink [mailto:will.pink@gmail.com]
Sent: Monday, August 04, 2008 7:08 AM
To: pound@apsis.ch
Subject: [Pound Mailing List] Problems with SSL

Hello all,

I have a Linux firewall server that is running pound that load balances
to a Windows Server which has a .NET App running on it, What I am having
problems with is the SSL termination for this server. I have placed the
cert on the Pound server and it listens on port 443 fine but when I try
and access the site with https it responds with An internal server error
occurred. Please try again later.
when I try http it says Firefox has detected that the server is
redirecting the request for this address in a way that will never
complete.
I know the app on the Windows server will do a rewrite from http to
https so I think this maybe the problem but is there a way of getting
this to work with pound? The way I thought of doing it would be to have
the cert on the Windows server and have pound listen on 443 and let
Windows serve the cert but I haven't been succesful so far.

Any help most appreciated,

Thanks,
Will


--
To unsubscribe send an email with subject unsubscribe to pound@apsis.ch.
Please contact roseg@apsis.ch for questions.

--
This message has been scanned for viruses and dangerous content by
SecureMail, and is believed to be clean.

--
To unsubscribe send an email with subject unsubscribe to pound@apsis.ch.
Please contact roseg@apsis.ch for questions.