Hi,
> Mainly because I can't seem to get it to work - nginx, apache or
> iptables.
>
> I'm sure someine can come forward with technical reasons why...
In this thread you asked about how this could be done, you didn't say
that you already tried something and that it didn't work.
So you are hopin
On Tue, 2014-03-25 at 16:29 +0100, Lukas Tribus wrote:
> Hi,
>
>
> > 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
>
Hi,
> 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
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 han
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 wrote:
> Is there any way of forward
