Learn about the health checks that check for cookie hijacking and protocol downgrade attacks protection.
Checks if your site, when running with HTTPS, contains the Strict-Transport-Security Header (HSTS).
How to fix this health checkThis health check can be fixed by adding the Strict-Transport-Security header to responses. The header tells browsers that future requests should be made over HTTPS only.
Enabling HSTS on a domain will cause browsers to only use HTTPS (not HTTP) to communicate with your site. Only enable HSTS on domains that can, and should, use HTTPS exclusively.
Using the UseHsts extension methodASP.NET Core implements HSTS with the UseHsts extension method.
You can add UseHsts after the env.IsDevelopment() check-in Program.cs.
if (builder.Environment.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseHsts();
}
//...
}This example only enables HSTS if the app is not running in development mode. UseHsts isn't recommended in development because the HSTS settings are highly cacheable by browsers.
It is possible to configure a timespan for the HSTS, preferably six months. This can be done by adding a new builder to the Program.cs file. Learn more in the official Microsoft Documentation .
Full details of UseHsts, and additional configuration, can be found in the ASP.NET Core documentation .
Last updated 4 months ago
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4