Fix HTTP basic authentication header detection for cURL example #110
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.
Unfortunately there is a bug in my previous pull request #108.
Headers in specs are written with a
HTTP_
prefix (e.g.HTTP_AUTHORIZATION
), and given without alteration to theCurl
class (source).When generating the API documentation, headers for
Curl
are set byClientBase
(source), which includesHeaders
which formats them nicely (e.g. "Authorization") (source).Therefore the spec is green, but the generated documentation does not show the username and password as desired. This pull request changes one line to use a regular expression to detect the authorization header, either written as
HTTP_AUTHORIZATION
orAuthorization
.