Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Drop SHOULD from 2.2.1 #640

Closed
estark37 opened this issue Jun 2, 2018 · 0 comments
Closed

Drop SHOULD from 2.2.1 #640

estark37 opened this issue Jun 2, 2018 · 0 comments
Assignees
@estark37
Labels
editorial expect-ct

Comments

@estark37
Copy link
Contributor

estark37 commented Jun 2, 2018

"2.2.1, the "SHOULD" here isn't a real requirement. You can drop it
and just say "an Expect-CT host includes exactly one Expect-CT header
field in its response". A host that isn't Expect-CT won't include the
header field." (http://lists.w3.org/Archives/Public/ietf-http-wg/2018AprJun/0238.html)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@estark37 estark37

Labels
editorial expect-ct
Milestone
No milestone
Development

No branches or pull requests
1 participant
@estark37