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

Misleading name for headers parameter #1181

Closed
richanna opened this issue May 25, 2020 · 0 comments · Fixed by #1297
Closed

Misleading name for headers parameter #1181

richanna opened this issue May 25, 2020 · 0 comments · Fixed by #1297
Labels
signatures

Comments

@richanna
Copy link
Contributor

The Covered Content list contains identifiers for more than just headers, so the header parameter name is no longer appropriate. Some alternatives: "content", "signed-content", "covered-content".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
signatures
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adopting Structured Fields richanna/http-extensions
2 participants
@mnot @richanna