If you're experiencing connection errors with Safari (and possibly other browsers), which fail to load one of your HTTPS sites served by Artica as a reverse proxy, it's possible that the backend is an Apache server.
It's possible that the backend is an Apache server.
We're talking about an eventuality with Apache, but it's possible that other backend servers behave in the same way.
When the reverse-proxy retrieves content from Apache using HTTP/1.1, the backend server attempts to switch to HTTP/2 by sending the "Upgrade: h2" header.
The reverse-proxy transmits the Upgrade header from the backend server to the browser.
Browsers on iOS (on iPhone) and Apple macOS High Sierra may fail here and interrupt the connection on such behavior.
This may be due to a different version of OpenSSL
To correct this, simply ask the reverse-proxy not to retransmit the "Upgrade" header from the backend
- Open a Web site rule and click on the “
Header Removal Rules” link
- Click on the button “
New rule” - Add Upgrade inside the the “
Remove HTTP Header” field. - The
Backend Onlyinstruct the reverse-proxy to only not reproduce the specified header from backend.
