Betrouwbare Webhosting

Port 443 - Support for HTTPS - SSLEngine

SSL Everywhere - Secure Connection

Is set to “on” by default (Default: on)

Any more?

Certificates (https://github.com/cheyenneq/no-save-redirects-plugin/issues/258)

Implementation

Webmaster: the browser does not save the GET parameter for HSTS until it receives a new http request

The browser automatically assumes that the resource is safe to send to the server, ie. has expired or is renewed, so if you want to stop this behaviour, do not save your redirection commands like HSTS anchor links, cookies, files, etc.

There are three ways to avoid this behavior in which case the next Redirect will be sent to the URL without parameters.

1. Disable reload after http redirect. This is not very straightforward and may invalidate the current redirect link if you happen to forget to unset the Redirect flag. I'm thinking that you would probably get a canonical redirect packet whenever you go directly back to the previous page (by removing the HSTS header).

2. Add https to your redirect instead of http. This is done by setting the www type to https. Check out the recent example. This is much more elegant and reliable than the first method.

3. If the page you want to redirect has the same version as the page that triggered the redirect, look into re-archiving pages that have the same hash key or similar filename, but differ only in their URL path. The main advantage here is that you will need at least the same version of the saved page to take the "extra steps" before the redirection happens again.

example:

Set a new Redirect String with: https://%s/…

Add your Redirect params to the HSTS header. e.g. (Redirect Parameter > no…)

Clear the browser cache

Only the redirect will be saved. No other changes will happen. Using your browser history might cause your browser to refresh when you go to the site again.

This prevents your auto-redirecting browsers from making you fill in the HSTS header information again.