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

Concerns regarding large Link headers with Link Hints #319

Open
RubenVerborgh opened this issue May 29, 2020 · 1 comment
Open

Concerns regarding large Link headers with Link Hints #319

RubenVerborgh opened this issue May 29, 2020 · 1 comment

Comments

@RubenVerborgh
Copy link

@RubenVerborgh RubenVerborgh commented May 29, 2020

Following Appendix A of https://tools.ietf.org/html/draft-nottingham-link-hint-02, the Link Hint JSON structure can be serialized in a Link header.

However, this seems to result in rather large Link headers, and it seems a strange precedent to stuff JSON in headers.

What is the design rationale behind this?
Aren't we better off just linking to a Link Hints document (which could be cached and, with HTTP/2, be pushed)?

@hvdsomp
Copy link

@hvdsomp hvdsomp commented Jun 29, 2020

Actually, the approach to provide a set of links in a dedicated document, as described in the "linkset" I-D, could be used for that purpose, see https://tools.ietf.org/html/draft-wilde-linkset-06.

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.