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

use of Link header #142

Open
aaronpk opened this issue Oct 25, 2017 · 2 comments
Open

use of Link header #142

aaronpk opened this issue Oct 25, 2017 · 2 comments

Comments

@aaronpk
Copy link
Member

aaronpk commented Oct 25, 2017

8: "The request MUST include at least one Link Header"

I am surprised by using Web Linking headers in a request. I cannot find a clear rule in RFC 5988 and have not checked other specifications yet that might do this. Is this allowed? I would guess that you at least need the "anchor" parameter, which sets the context to the resource URL. Has someone checked this, e.g., with Mark Nottingham?


From #127 by @mkovatsc

@aaronpk
Copy link
Member Author

aaronpk commented Nov 16, 2017

I hadn't really considered whether it's "allowed" or not. PubSubHubbub has used this feature for years, so it's at least relatively widely implemented.

@aaronpk
Copy link
Member Author

aaronpk commented Nov 21, 2017

We discussed this on the call today. After looking into the two specs that WebSub references (RFC 7231 and RFC 5988), neither of those disallows the use of Link headers in a request. Additionally, the author (Mark Nottingham) has previously indicated that the Link header is intended to be allowed in HTTP requests, not just responses. As such, the group resolved to close this issue with no change, since the spec is very clear about the intent and there should be no confusion about what an implementation should do.

The request MUST include at least one Link Header [RFC5988] with rel=hub...

@mkovatsc please let us know if this addresses the issue for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant