Configuring host root replacements

Implemented in V5.0.1.8, extended in V5.0.2.0

Clients are normally connecting to a server farm using the https: protocol, but in rare situations, an advanced firewall in front of the farm is connecting to the real server on the secure side through the http: protocol to save resources on firewall and server not having to reencrypt traffic at the firewall and decrypt it again on the server.The real server doesn't know that it is really being addressed through https: from the client, and as it only knows its own hostname with a http: binding, it will issue links at the client side pointing to an http: based URL.

The settings below allows you to specify search and replace on the host path of the real server before it is returned as URLs to the client:

  <applicationSettings>
    <Plass.Id.Web.Properties.Settings>
		.....
      <setting name="HostRootReplacementKey" serializeAs="String">
        <value>http:</value>
      </setting>
      <setting name="HostRootReplacementValue" serializeAs="String">
        <value>https:</value>
      </setting>
		..... 
    </Plass.Id.Web.Properties.Settings>
  </applicationSettings>

Line 5 http: is the text to search for and line 8 https: is the replacement value.

The settings will allow you to search any consecutive part of the host path, so you may specify more than the protocol to be replaced if necessary, in example if the URL includes a port designation such as ':80' for port 80, you would change it to :443 if you also changed http to https.

You can also specify another two key/value pairs In case you need multiple replacements. They are "HostRootReplacementKey2", "HostRootReplacementValue2", "HostRootReplacementKey3" and "HostRootReplacementValue3".

All replacements are done in consecutive order on each resulting string, and further replacements are skipped if a key is empty, so you must start with HostRootReplacementKey, then Key2 and finally Key3 if necessary. 

Please be aware that extensive replacements could be detected as cross-site scripting and blocked by other security features on your server, and you will need to solve such issues yourself.