Redirecting HTTP to HTTPS

EFT Server's HS-PCI module allows you to redirect HTTP connections to HTTPS. If you do not activate the HS-PCI module, this feature is disabled after the 30-day trial expires.

If you have configured HTTPS transfers on the Site, you can redirect HTTP to HTTPS at the Site level. Doing so disables HTTP transfers.

The Server simply tells the connecting client that the resource was moved to the new HTTPS URL. The connecting client decides whether it will allow the redirect, because the new URL could on different server.

In general, the redirect process includes the following steps:

1. Client sends a request to the HTTP port (by default, port 80).

2. EFT Server redirects all plain HTTP requests to HTTPS (by default, port 80 to port 433). EFT Server replies to the client with 302 code (the requested resource resides temporarily under a different URL), and sends to the client the new URL where the resource is now located.

3. The client now know that the resource is not available at the old URL and knows the new URL. Client decides whether it wants to connect new URL and get this resource.

Refer to RFC 2616, section 10, http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html, for more information about redirection on HTTP.

The redirect HTTP to HTTPS option affects incoming AS2 requests through HTTP. If the connecting AS2 client does not allow redirection to a different port, the connection will fail.

To redirect HTTP to HTTPS

1. In EFT Administrator, connect to EFT Server and click the Server tab.

2. In the left pane, click the Site you want to configure.

3. In the right pane, click the Connection Options tab.

4. Select the Redirect HTTP to HTTPS check box. The Allow HTTP Transfers on port check box becomes unavailable.

5. Click Apply to save the changes on EFT Server.

Related Topic

Registry Settings