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

SEARCH spec shouldn't use text/query mime type #1450

Closed
pimterry opened this issue Apr 8, 2021 · 1 comment
Closed

SEARCH spec shouldn't use text/query mime type #1450

pimterry opened this issue Apr 8, 2021 · 1 comment

Comments

@pimterry
Copy link

pimterry commented Apr 8, 2021

Minor point, but this is a non-standard mime type (in fact when googling for Content-Type: text/query the HTTP SEARCH spec is the top result). That's not prohibited, but it seems like this spec shouldn't implicitly mint a new mime type for this query syntax, or encourage users to create their own custom mime types when it's not necessary.

The spec seems to use a SQL dialect: select surname, givenname, email limit 10. Given that, it seems like we could use application/sql instead (which is standardized).

@reschke
Copy link
Contributor

reschke commented Apr 8, 2021

It's just an example. We'll get to this later.

@reschke reschke closed this as completed in b7c0cb5 Jun 8, 2021
reschke added a commit that referenced this issue Jun 8, 2021
use example media type (closes #1450)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants