Configuring HTTP settings for the Delphix engine

Use the following steps to configure HTTP settings for the Delphix Continuous Data Engine.

1. Login to the Continuous Data Setup UI as a sysadmin.

2. From the Dashboard, select Settings under Network Security. This will open a new wizard where you can modify the settings. 

   

3. In the Network Security Settings screen, you can modify the HTTP mode, TLS Version, and HTTPS Ciphers to be used.

4. In HTTP mode, select one of the following:

   1. HTTP Only – accepts only HTTP connections.

   2. HTTPS Only – accepts only HTTPS connections.

   3. HTTP Redirect – redirect all requests made over HTTP to HTTPS.

   4. HTTP and HTTPS – accepts both HTTP and HTTPS connections.

   5. HTTP Redirect with HSTS – redirect all requests made over HTTP to HTTPS and add the “Strict-Transport-Security” header to all responses.

      1. HSTS is not required. By default, the Continuous Data Engine is configured to HTTP and HTTPS. This can be left as is.

      2. If you set up HSTS and want to revert it, follow the same steps to this point and select your previous option.

         

5. In TLS Version, select the required TLS versions.

6. In HTTPS Ciphers, select the required option from the drop-down list. Click the check box next to Select All to choose all options.

7. Click Next and then click Submit, allowing your engine to restart for the changes to take effect.

8. When the Continuous Data Engine homepage is loaded after the restart, all the HTTP requests will be redirected to the selected HTTP mode after the first load.

The above steps could fail if:

1. The certificates are not trusted – a “not secure” warning on the search bar of the browser. Certificate setup should be completed before setting up HSTS headers in order for them to be useful. Otherwise, the redirect will still happen over 302 status.

2. Your site is not prepared for HTTPS setup – for example, each of the subdomains accessed should be supporting HTTPS; parts of the application might be inaccessible otherwise.

3. Every first request whenever the cache is cleared would redirect over 302. Any further requests after the first would redirect over 307