Debugging method for "Force-https-links" & "X_SSL to decrypted" headers (HTTPS offloading)

The next steps explain how to check if the "Force-https-links" & "X_SSL to decrypted" headers are well defined from your CDN to the CHILI Server and reaching the CHILI Server.

Checking these headers is possible by enabling advanced logging on IIS and is the only way to be sure:
https://docs.microsoft.com/en-us/iis/extensions/advanced-logging-module/advanced-logging-for-iis-custom-logging#server_logging

If "Advanced Logging" is not available, (which is an optional Microsoft component), you can download it here:
https://docs.microsoft.com/en-us/iis/extensions/advanced-logging-module/advanced-logging-readme

 Follow the next steps to enable the logging

 1. Add logs fields similar to the following screen for X_SSL and Force-https-links.

Open

2. Be sure they are visible in log selection, if not, edit and select them

Open

3. Enable "Advanced logging" on the menu panel on right.

4. Make a request to the server.

5. Browse to the log directory (similar to C:\inetpub\logs\AdvancedLogs ) and open the latest file.

6. Analyse the log file:

The content of the log file should contain lines like the examples below.
The info that you should be looking for in the log files is highlighted in bold. 

If you are seeing this information, the CDN is sending the headers correctly.
(The example contains a request for an editorURL (what you get returned for the webservice calls "DocumentGetEditorURL" or "DocumentGetHTMLEditorURL"), and is represented as #editorURL#)

#Fields:  date time cs-uri-stem cs-uri-query s-contentpath sc-status s-computername cs(Referer) sc-win32-status sc-bytes cs-bytes X_SSL Force-https-links

2018-03-20 16:33:43.620 /CHILI/scripts/CHILI/DefNS.js - "C:\CHILI_Publisher\app\scripts\CHILI\DefNS.js" 200 "DE-CS01" - 0 5487 253 - -

2018-03-20 16:33:44.606 /CHILI/main.asmx wsdl&client_app=CHILI_Editor "C:\CHILI_Publisher\app\main.asmx" 200 "DE-CS01" "#editorURL#" 0 729 3025 "decrypted=true" "ON"