moving servers... https woes.

[Steve Holdoway]

Hi Lorne,

Sadly not quite. The change in IP means that the eCommerce part of the
site must be served through https:, but there seems to be a terrible lag
- even though TTL has been set to 5 minutes for weeks - for customers in
picking the change up.

This means that the old IP address needs to handle and forward http and
https, as well as the new one - which means that I can't just terminate
https at the old IP and proxy as http: as the new server forces it back
to https:

Confused? Me too!


Cheers,

Steve

On Mon, 2014-03-24 at 22:02 -0300, Lorne Wanamaker wrote:
> Not quite sure if I understand right but you may be able to do this
> using maps. Something like:
> 
> 
> http://redant.com.au/ruby-on-rails-devops/manage-ssl-redirection-in-nginx-using-maps-and-save-the-universe/
> 
> 
> 
> Lorne
> 
> 
> On Mon, Mar 24, 2014 at 8:51 PM, Steve Holdoway
> <steve at greengecko.co.nz> wrote:
>         Is there any way of forwarding https to a new server while
>         people's DNS
>         and browsers drain down? I know it's easy enough to terminate
>         it and
>         forward http, but I need both the old and new sites
>         ( ecommerce ) to
>         work in https where relevant...
>         
>         I have a horrible feeling that you can't.
>         
>         Cheers,
>         
>         
>         Steve
>         --
>         Steve Holdoway BSc(Hons) MIITP
>         http://www.greengecko.co.nz
>         Linkedin: http://www.linkedin.com/in/steveholdoway
>         Skype: sholdowa
>         
>         _______________________________________________
>         nginx mailing list
>         nginx at nginx.org
>         http://mailman.nginx.org/mailman/listinfo/nginx
> 
> 
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

-- 
Steve Holdoway BSc(Hons) MIITP
http://www.greengecko.co.nz
Linkedin: http://www.linkedin.com/in/steveholdoway
Skype: sholdowa