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.

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

Extend Accept-Signature to include app/s-e response type #470

Open
twifkak opened this issue Jul 26, 2019 · 1 comment
Open

Extend Accept-Signature to include app/s-e response type #470

twifkak opened this issue Jul 26, 2019 · 1 comment
Labels
needs spec The issue has agreement, but someone needs to add it to the specification.

Comments

@twifkak
Copy link
Collaborator

twifkak commented Jul 26, 2019

The Accept-Signature header says:

When a server receives an Accept-Signature header field in a client request, it SHOULD reply with any available Signature header fields for its response that the Accept-Signature header field indicates the client supports.

However, the same-origin Signature response may be less reliable than application/signed-exchange, due to possible undesired transformations of signed data (headers or payload). Consider modifying this section to say that a server MAY reply with an application/signed-exchange instead.

@jyasskin
Copy link
Member

That sounds like a good change.

@jyasskin jyasskin added the needs spec The issue has agreement, but someone needs to add it to the specification. label Aug 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs spec The issue has agreement, but someone needs to add it to the specification.
Projects
None yet
Development

No branches or pull requests

2 participants