swagger-api / swagger-api/swagger-codegen
Content-Type header charset
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
When using generated Java client, requestBuilder is using MediaType class
I don't want to add ;charset=utf-8 to the Content-Type header, how can I control the parse method not to add it by default?
Contributor guide
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 with the generated Java client's requestBuilder and the MediaType class, then trace the parse method that adds the Content-Type charset. Check how the generated client represents this header and whether existing configuration points are involved. Done means the charset behavior is clearly controllable and covered by the relevant client behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100