4 ms·
Probably because you didn't include the content type header?
by tvink 9mo ago
Probably because you didn't include the content type header?
- therealwardo 9mo agoyep that would fix it. just needs a little docs change. a "quick start" really should just work when you copy paste them.
- rendaw 9mo agoCan it be some other content type?
- ch2026 9mo agowhy does an API that only accepts json need me to specify in a header that it’s json. just assume it’s json. you’re gonna parse and validate it anyway.
- cess11 9mo agoIf it turns out that someone is willing to pay for some other protocol then they just have to hook it up to that MIME type and start serving. It might be possible that they can derive an implementation of that protocol from their data schemas. If they hardcode JSON such a change would be breaking for their previous users.
- anamexis 9mo agoWhy would it be a breaking change? Just continue assuming JSON if no Content-Type is provided.
- bflesch 9mo agothat's actually a reasonable point.