Quoted-string Basic realm ctx according to rfc7235 #13
Conversation
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
Hi, I faced some problems with 401 message and an Android client. It yelded because in the WWW-Authenticate header the Basic ream=<ctx> wasn't surrouned by "" In the https://tools.ietf.org/html/rfc7235 it is written that - Authentication parameters are name=value pairs - and "auth-param = token BWS "=" BWS ( token / quoted-string )" - and "For historical reasons, a sender MUST only generate the quoted-string syntax. Recipients might have to support both token and quoted-string syntax for maximum interoperability with existing clients that have been accepting both notations for a long time." After my modification, the Android worked again (and iOs and PC clients faicing the 401 still worked ;) ) BR, Arfy
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.
Hi,
I faced some problems with 401 message and an Android client.
It yelded because in the WWW-Authenticate header the
Basic ream=
wasn't surrouned by ""
In the https://tools.ietf.org/html/rfc7235 it is written that
syntax. Recipients might have to support both token and
quoted-string syntax for maximum interoperability with existing
clients that have been accepting both notations for a long time."
After my modification, the Android worked again (and iOs and PC clients faicing the 401 still worked ;) )
BR,
Arfy