Hi,
In Settings > Web and HTTP > Security, we can set custom headers, using semicolon ';' as a separator between multiple headers.
This is mostly because they want to use a custom header for Strict-Transport-Security, which dictates we should really use semi-colons (as values after the comma are sometimes ignored). Here are some sources:
- https://datatracker.ietf.org/doc/html/rfc6797#section-6.1
- https://infosec.mozilla.org/guidelines/web_security#http-strict-transport-security
- https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html#examples
In our case we had to customize it (which was not a big deal):
- We disabled the checkbox for "Enable 'Strict-Transport-Security: max-age={expire-time}' header - HTST" - had to any way
- We removed the value from Custom Headers
- We updated the CustomHeaderInclude.cshtml template (it's a Swift site) with
	- 
		Dynamicweb.Context.Current.Response.AddHeader("Strict-Transport-Security", "max-age=31536000; includeSubDomains; preload");
 
- 
		
But I wonder if the platform should consider changing the behavior of Custom Headers so we can use it properly? Because this would introduce a breaking change, maybe using a Feature flag to hide the current field and add a new one that would handle it differently?
Best Regards,
Nuno Aguiar
 
                                             
                                         
                                                             
															 
								 
								 
															 
															 
															 
								 
								 
								