fix: swagger Authorize bearer steps (local 401) - #30
Merged
Merged
Conversation
Swagger was also generating an Authorization parameter defaulting to "Bearer " which overwrote a good Authorize value. Rely on BearerAuth only; document exact UI steps (Bearer dev, not just dev).
Default proxy GET url to https://httpbin.org/get (echoes headers/method). Status 418, delay 2s, probe mode examples, clearer Authorize-only auth text.
Split proxy GET/POST handlers so Try it out does not send a body on GET (browser fetch error). Refresh top swagger title/description for the cluster-debug story. Default GET url remains httpbin.org/get.
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Swagger UI 401 with a correct token was often the duplicate Authorization
parameter (default
Bearerwith no token) fighting the Authorize dialog.@Param Authorizationon secured opsBearer dev