You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem.
When the redirectUrl is returned in the following format: http://url?code=abc;state=xyz
AuthorizationCodeResponseUrl doesn't parse it properly, as it only accepts & as the separator.
The text was updated successfully, but these errors were encountered:
wonderfly
added
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
imported
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
labels
Jan 9, 2015
Although technically acceptable, Google APIs in general do not allow ; as query parameter. Changing this to a feature request.
chingor13
added
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
and removed
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
labels
Jul 17, 2018
From ykph...@gmail.com on February 06, 2014 18:48:21
Version of google-oauth-java-client (e.g. 1.5.0-beta)?
1.15.0-rc
Java environment (e.g. Java 6, Android 2.3, App Engine)?
Android 4.1
Describe the problem.
When the redirectUrl is returned in the following format:
http://url?code=abc;state=xyz
AuthorizationCodeResponseUrl doesn't parse it properly, as it only accepts & as the separator.
As per: http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2 Semicolon should also be accepted as the separator for the parameters. How would you expect it to be fixed? It should parse the code and state properly when semicolon is used as a separator.
Original issue: http://code.google.com/p/google-oauth-java-client/issues/detail?id=89
The text was updated successfully, but these errors were encountered: