3 ms·
> some web frameworks do content negotiation by appending a content type like .json to the end of the url This has always disturbed me, considering that HTTP h
by jfrunyon 5y ago
> some web frameworks do content negotiation by appending a content type like .json to the end of the url
This has always disturbed me, considering that HTTP has had content negotiation for ... oh, basically its entire history [https://www.w3.org/Protocols/HTTP/1.0/spec.html#Accept https://www.w3.org/Protocols/HTTP/1.0/spec.html#Accept].
- Macha 5y agoFor non-programmatic usage and verification, the extensions can be easier? On a similar topic HIBP allowed people to request versioning via a custom HTTP Header, a Accept Content-Type, or a version segment in the URL path and approximately everyone went with option 3.
- jfrunyon 5y ago"For non-programmatic usage and verification," it should be served in a human-readable manner, typically including things like formatting, and maybe even syntax coloring if you're feeling nice. Take my `Accept: text/html` and give me my HTML-ified JSON, dangit! ;)
- Macha 5y agoI've actually seen APIs with "pretty=true" or "indent=4" type query parameters to emit formatted JSON for people before, though it doesn't go as far as HTML with syntax colouring.