You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just my 2 cents: The FGT services operate entirely in HTTP (not HTTPS), as it normally operates on port 8080 (not 443).
It is up to the surrounding infrastructure, if desired to have the service reverse-proxied by HTTPS, to add the HSTS header (if desired).
Reponse proposal: The code is designed for http (not https). Makes no sense to add an Strict-Transport-Security header on an http response in this situation. When deploying a production environment, the solution will probably be wrapped by a reverse https-to-http proxy. It is up to that proxy to add the Strict-Transport-Security header if desired.
implement HSTS headers for the API
The text was updated successfully, but these errors were encountered: