On Jul 14, 2009, at 6:40 PM, John Oliver wrote:
On Tue, Jul 14, 2009 at 05:50:13PM -0500, Doug Bell wrote:
On Jul 14, 2009, at 5:25 PM, John Oliver wrote:
I have a server that's always been known as https://server1.com/
It's
now known as https://server2.com/ Anyone who accesses it as
http
On Tue, Jul 14, 2009 at 05:50:13PM -0500, Doug Bell wrote:
> On Jul 14, 2009, at 5:25 PM, John Oliver wrote:
>
> >I have a server that's always been known as https://server1.com/ It's
> >now known as https://server2.com/ Anyone who accesses it as
> >https://server1.com/ winds up getting a certif
On Jul 14, 2009, at 5:25 PM, John Oliver wrote:
I have a server that's always been known as https://server1.com/ It's
now known as https://server2.com/ Anyone who accesses it as
https://server1.com/ winds up getting a certificate error as well as
other issues. I want to grab and rewrite any h
I have a server that's always been known as https://server1.com/ It's
now known as https://server2.com/ Anyone who accesses it as
https://server1.com/ winds up getting a certificate error as well as
other issues. I want to grab and rewrite any https://server1.com/ URLs
to https://server2.com/ B
