This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 674
Use request accept header to distinguish json status #1063
Comments
rade
changed the title
Use request content type header to distinguish json status
Use request accept header to distinguish json status
Jul 5, 2015
@tomwilkie @squaremo Are we ok with just matching on |
rade
added a commit
that referenced
this issue
Jul 5, 2015
...instead if having a separate URL. Closes #1063.
That's what I've done. |
Yes I think that sufficient. We're not expecting browsers to hit this endpoint, so full content negotiation is probably not required. |
The JSON endpoint was specifically written for my browser to hit. Could you expand on what other use-cases you had in mind? |
Your browser, or an app running in your browser? |
Javascript running in my browser. |
The javascript has control over the headers it sends, and therefore can request json if it wants it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
...instead of having a
status-json
url path.The text was updated successfully, but these errors were encountered: