Explicit responses should bypass error pages
Open
Feedback Wanted
UX
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 383
- PR merge metrics
- No merged PRs in 30d
Description
Currently if `text/html` is accepted, Up will serve the error page. It seems common for people to `fetch()` or `curl` without explicitly setting `Accept: application/json` or similar, resulting in the HTML which can be confusing.
We could disable error pages by default, or maybe drop content negotiation and assume non-text/plain responses are intentional, something like that.
Note to self: at least document Accept usage
Contributor guide
Assessment
This issue has not been assessed yet.