Moving servers https woes

Server NGINX
1

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 H. BSc(Hons) MIITP

Linkedin: http://www.linkedin.com/in/steveholdoway
Skype: sholdowa

2

Not quite sure if I understand right but you may be able to do this
using
maps. Something like:

Lorne

3

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:

    I have a horrible feeling that you can't.

    _______________________________________________
    nginx mailing list
    [email protected]
    http://mailman.nginx.org/mailman/listinfo/nginx

nginx mailing list
[email protected]
nginx Info Page

–
Steve H. BSc(Hons) MIITP

Linkedin: http://www.linkedin.com/in/steveholdoway
Skype: sholdowa

4

On Tue, 2014-03-25 at 16:29 +0100, Lukas T. wrote:

https at the old IP and proxy as http: as the new server forces it back
to https

I’m probably missing something, but why don’t you just forward https to
https and http to http?

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…

Steve

–
Steve H. BSc(Hons) MIITP

Linkedin: http://www.linkedin.com/in/steveholdoway
Skype: sholdowa

5

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 hoping that someone may be able to provide the technical
reason for a failure you didn’t even mention in the first place (let
alone
some details)?

As for your original question, I would configure the old server like
this,
to pass the requests to the new server:

server {
listen 80;
location / {
proxy_pass http://:80;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
}
}
server {
listen 443 ssl;
location / {
proxy_pass https://:443;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
}
}

Regards,

Lukas

6

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 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

I’m probably missing something, but why don’t you just forward https to
https and http to http?

Regards,

Lukas