Set v3 Content-Type Response Header As JSON
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
v3 response header content-type is set as text/plain. It would be better to set it as application/json as the responses are actually JSON. Also it'll help many GUI tools (e.g. Postman) to render them properly automatically.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Burrow v3 response handling and the code that sets the Content-Type header. Verify the current text/plain behavior with an API request, then confirm that responses are reported as application/json and that relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100