I'm trying to configure nginx as reverse proxy (cache) for a website that runs Apache + Wordpress and that is configured to redirect all HTTP traffic to HTTPS. To this end I'm trying to disable the HTTPS redirection in Apache/Wordpress (origin server).
Let alone nginx, a working copy of the origin server (Apache) is at http://test.assodigitale.it:14580 and here is what I've done so far:
- Removed the "Redirect 301 https://..." from the virtual host
- Removed .htaccess
- Disabled all WP plugins
- Replaced in the database all
http://test.assodigitale, including serialized Wordpress strings
- Disabled mod_http2
- Commented out
Protocols h2 h2c http/1.1from apache config
- Checked that no HSTS configuration is in place
However all I obtained is that the server replies plain HTTP only, but the redirection of the browser to HTTPS is still taking place and it causes the obvious SSL error you see by clicking the link above.
I'm overlooking something, but I don't understand what, and I don't know how to trace the communication between the browser and the server to pin down the guilty configuration. Can you help please?
EDIT AFTER COMMENTS:
I'm using Apache because I need it for reasons beyond the scope of this question. I know I could do everything with nginx only, but please ignore nginx while considering the problem. I've included it in my question only to give a context, but the problem is there regardless of nginx. It's Apache listening to port 14580 and it's Apache or something else after it redirecting the browser, not nginx that sits before Apache and that, by the way, at the moment is not even listening to port 80 (hence the connection refused when connecting to port 80 as reported by madeddie).
However madeddie reports also that the server redirects his browser to port 80, while in my case I got redirected to port 443, which makes me wonder how come the server is even issuing different redirects to me and to him...