swagger-api / swagger-api/swagger-ui
How to use HTTP2 with the swagger editor request execution?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
How can we help?
Using the online swagger editor UI with a OPEN API spec. When trying to execute a GET or POST request it is using HTTP1. Is there a way the UI can try it with HTTP2 instead ? I want to avoid using curl and would like to use the GUI if possible to do it. Thanks.
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 online Swagger Editor UI's request-execution entry point and determine how it selects the HTTP protocol for GET and POST requests. Confirm whether HTTP/2 can be enabled through the UI, then define completion as executing the request over HTTP/2 or documenting that the capability is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100