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

Structured Syntax Suffix support? #15

Open
dkubb opened this issue Jul 6, 2015 · 2 comments · May be fixed by #48
Open

Structured Syntax Suffix support? #15

dkubb opened this issue Jul 6, 2015 · 2 comments · May be fixed by #48

Comments

@dkubb
Copy link

dkubb commented Jul 6, 2015

Are there any plans to support the Structured Syntax Suffix RFC: http://trac.tools.ietf.org/html/draft-ietf-appsawg-media-type-suffix-regs-02

Specifically I would want to be able to use the +json suffix as defined in http://trac.tools.ietf.org/html/draft-ietf-appsawg-media-type-suffix-regs-02#section-3.1 with a wildcard like the following:

application/*+json

It would also be nice to be able to even be able to specify:

*/*+json
@zmthy
Copy link
Owner

zmthy commented Jul 13, 2015

No, but I'd welcome a pull request. Can you provide a use case for this functionality?

@dkubb
Copy link
Author

dkubb commented Jul 14, 2015

In an API that I work on, we can accept a valid JSON request whether it's application/json or a vendor tag like application/vnd.something+json. The +json suffix says that the media follows the same parsing rules as application/json. Granted we do currently just hard-code the specific media types, but it would be nice to be able to specify a wildcard instead.

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

Successfully merging a pull request may close this issue.

2 participants