swagger-api / swagger-api/swagger-ui
Example request begins with Unauthorized OPTIONS request
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: macOS
- Browser: Firefox
- Version: [e.g. 22]
- Method of installation: docker container (swaggerapi/swagger-ui:v5.12.0)
- Swagger-UI version: 5.12.0
- Swagger/OpenAPI version: Swagger 2.0
Content & configuration
How can we help?
When executing an example from the Swagger-UI, an unauthorized OPTIONS request is sent,
which in my case is replied with a '401 Unauthorized'. So my question is if there is a way
around this (I can't change my endpoint to allow Unauthorized request)?
Cheers, Toby
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 by reproducing the example request in Swagger UI 5.12.0 from the swaggerapi/swagger-ui:v5.12.0 Docker image, using the reported Swagger 2.0 setup in Firefox on macOS. Inspect the browser network request and the supplied endpoint's authentication response; done means determining whether the unauthorized OPTIONS request is expected and documenting an actionable resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- api, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100