-
Notifications
You must be signed in to change notification settings - Fork 328
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
Standardize "nosniff" #35
Comments
👏 |
I wrote a gecko bug to implement this for fetch: https://bugzilla.mozilla.org/show_bug.cgi?id=1150897 Our older general "nosniff" bug: |
@annevk https://tools.ietf.org/html/rfc6648 ... can we drop the X-? /cc @mnot |
@igrigorik that would break existing content. |
Hmm, I guess a broader question then.. For places where we use |
I think we should just leave it and not add complexity. And in the future avoid inventing |
Yep, that RFC is for new things, not existing things. If you need to make a breaking change on one of those headers, that's your opportunity to change the name, but don't do it just to change the name; that's a worse outcome. |
Research:
Todo:
Tentative plan:
X-Content-Type-Options
header.Open issue:
The text was updated successfully, but these errors were encountered: