Skip to content

Support Accept and Accept-Encoding #53

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

Open
sfackler opened this issue Oct 25, 2019 · 4 comments
Open

Support Accept and Accept-Encoding #53

sfackler opened this issue Oct 25, 2019 · 4 comments

Comments

@sfackler
Copy link
Contributor

No description provided.

@DusterTheFirst
Copy link

Is there any reason for this not moving forward?

@coriolinus
Copy link

At a guess, it's because the Accept specification is complicated, and it's not a super high priority for Hyperium team members right now.

I'm working on an implementation right now, but no idea what the response would be to a PR upstreaming it.

@coriolinus
Copy link

https://github.com/coriolinus/accept-header

@maxcountryman
Copy link

After surveying the crate ecosystem, I found that third party Header implementations either:

  1. Depended on the "rotting" mime crate or
  2. Deviate from the spec.

And in some cases both.

Also the linked crate above is not available via crates.io.

So I published headers-accept which addresses these issues: it uses the mediatype crate instead of mime and adheres to spec without e.g. sorting when not called for by the spec. It also incorporates the spec-compliant parsing technique used by mediatype.

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

No branches or pull requests

4 participants