-
Notifications
You must be signed in to change notification settings - Fork 25.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enforcing HTTPS enhancements #9044
Conversation
ce1aaa6
to
7e89fd3
Compare
Add links Fix bookmark Updates
d982b32
to
a3bb4c4
Compare
I really don't like the structure of this document. It seems to be focused around the RequireHttpsAttribute which only works in MVC whereas the URL Rewriting middleware is just mentioned in passing. From this doc, it is by no means obvious that adding the RequireHttpAttribute even globally via MvcOptions does nothing to mitigate static files (as an example of another middleware) being served without TLS I'd rather we focus on the URL Rewriting middleware, and mention using the RequireHttpsAttribute more as a defense in depth mechanism |
I'll give that a shot on the next pass. |
@shirhatti did you read the 1.0 version of the doc? The 2.2 version says "Do not use RequireHttpsAttribute", use UseHttpsRedirection instead. |
@shirhatti Do you need doc structural changes (or was it the 1.x version loading)? |
🤦♂️ Turns out I was looking at the wrong version of the doc. |
@scottaddie I'll come back to this shortly and check the comments ... I'm still buried in Health Checks code atm. |
@scottaddie I fixed up those clickjacking sections into ordered lists as you suggested ... good call. 👍 I'm going to merge this after the build completes. |
@scottaddie Unapproved tab names. I'll fix those up first ... then merge it after it passes. |
Addresses #6538
Internal Review Topic
Organize and enhance the coverage. I've marked this "addresses" for now, but we might find out that other issues cover the remaining parts of #6538 and this PR can close the issue.
Numbering the items from #6538 for reference ...
a. Cross-link to existing server specific guidance on enabling HTTPS
b. Cross-link to the proxy guidance especially around validating forwarded headers Addressed by Forwarded headers updates for Nginx/Apache topics #6644.
There are other related issues on this subject, and I don't think we should try to address all of them on this PR.