Daniel Watts wrote:
> Paul Lesniewski wrote:
>> On 6/28/07, Daniel W <[EMAIL PROTECTED]> wrote:
>>> Paul Lesniewski wrote:
On 6/28/07, Daniel Watts <[EMAIL PROTECTED]> wrote:
> Dear List,
>
> Has anyone got a setup where you have a Pound front end reverse-proxy
> listening for
Paul Lesniewski wrote:
> On 6/28/07, Daniel W <[EMAIL PROTECTED]> wrote:
>> Paul Lesniewski wrote:
>>> On 6/28/07, Daniel Watts <[EMAIL PROTECTED]> wrote:
Dear List,
Has anyone got a setup where you have a Pound front end reverse-proxy
listening for HTTPS traffic, and redirectin
On 6/28/07, Daniel W <[EMAIL PROTECTED]> wrote:
> Paul Lesniewski wrote:
> > On 6/28/07, Daniel Watts <[EMAIL PROTECTED]> wrote:
> >> Dear List,
> >>
> >> Has anyone got a setup where you have a Pound front end reverse-proxy
> >> listening for HTTPS traffic, and redirecting via HTTP to a batch of
>
Paul Lesniewski wrote:
> On 6/28/07, Daniel Watts <[EMAIL PROTECTED]> wrote:
>> Dear List,
>>
>> Has anyone got a setup where you have a Pound front end reverse-proxy
>> listening for HTTPS traffic, and redirecting via HTTP to a batch of
>> backend web servers that squirrelmail is installed on?
>>
On 6/28/07, Daniel Watts <[EMAIL PROTECTED]> wrote:
> Dear List,
>
> Has anyone got a setup where you have a Pound front end reverse-proxy
> listening for HTTPS traffic, and redirecting via HTTP to a batch of
> backend web servers that squirrelmail is installed on?
>
> I have this working nicely ex
Dear List,
Has anyone got a setup where you have a Pound front end reverse-proxy
listening for HTTPS traffic, and redirecting via HTTP to a batch of
backend web servers that squirrelmail is installed on?
I have this working nicely except that the links and redirects are all
then written as "ht