swagger-api / swagger-api/swagger-ui
Accept-Encoding header not change according to customer value
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Q&A (please complete the following information)
- OS: Window
- Browser: chrome
- Version: 119.0.6045.160
- Method of installation: cdn
- Swagger-UI version: 5.0
- Swagger/OpenAPI version: OpenAPI 3.0
I am using swagger-ui to send a request with custom accept-encoding header but the request's header always is the default value "gzip, deflate, br".
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
No source file or test is named in the report. Reproduce the request in Swagger UI 5.0 with OpenAPI 3.0 and Chrome, then trace where the custom Accept-Encoding value is handled. Done means the configured value is sent instead of the default, with a regression test or a documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100