-
-
Notifications
You must be signed in to change notification settings - Fork 680
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
Consider removing requirement for Content-Disposition: attachment; filename header #1004
Comments
I think this issue is duplicate: #721 |
Quite possibly. I didn’t want to hijack that ticket. |
Neil, it's ok to keep the conversation here. You've given a very clear technical reason why the requirement is not helpful and I'm ready for a PR to remove it. If you PR I'll take care of it and handle the label. We're GTG on this. |
I'm ok with removing it. |
NeilMadden
pushed a commit
to NeilMadden/ASVS
that referenced
this issue
May 27, 2021
jmanico
added a commit
that referenced
this issue
May 27, 2021
#1004 Delete 14.4.2 requiring Content-Disposition on API responses
14.4.2 deleted |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requirement 14.4.2 says:
It's not clear that this actually prevents any current attack, as RFD attacks are (I believe) prevented by all modern browsers. See also this related issue on the W3C Post-Spectre web development spec.
The text was updated successfully, but these errors were encountered: