mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2360] HSTS Header is added on HTTP hosts - Incorrect implementation of RFC6797 #1672
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1672
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @StanvanHoorn on GitHub (Nov 3, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2360
Checklist
jc21/nginx-proxy-manager:latestdocker image?NoNoNoDescribe the bug
HSTS is added in the server block of the Nginx for both port 80 and 443 resulting in warnings in various online tooling including hstspreload.org. This probably is caused by the fact that the generated Nginx config combines the port 80 and 443 servers. See:
#1 - Redirection host template;
#2 - Listen config;
#3 - HSTS config
Possible solution
Make different server config blocks for port 80 and 443, and only include the HSTS config in the one for 443 if enabled.
Nginx Proxy Manager Version
v2.9.18
@StanvanHoorn commented on GitHub (Dec 1, 2022):
Any plans to fix this?
@github-actions[bot] commented on GitHub (Feb 6, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@StanvanHoorn commented on GitHub (Feb 9, 2024):
As far as I know, this issue still persists
@github-actions[bot] commented on GitHub (Nov 20, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Dec 3, 2025):
Issue was closed due to inactivity.