OAuth2 redirect should handle existing URL parameters

[ghost]

If the redirect already has a query string, e.g. https://example.com/?someparam=somevalue

and I construct the authorize URL as https://delicious.com/auth/authorize?client_id=a_client_id&redirect=https%3A%2F%2Fexample.com%2F%3Fsomeparam%3Dsomevalue, I'm redirected to https://example.com/?someparam=somevalue?code=a_code rather than the correct value of https://example.com/?someparam=somevalue&code=a_code

Bonus bug: redirect is a required parameter in the documentation, but the authorize page still loads without it.

[paoloramos]

I would like to report that I'm facing the exact same issue.

@voltagex : Have you by any chance found a solution to this?

[ghost]

No solution here

On 28 August 2014 00:04, paoloramos [email protected] wrote:

I would like to report that I'm facing the exact same issue.

@voltagex https://github.com/voltagex : Have you by any chance found a
solution to this?

—
Reply to this email directly or view it on GitHub
#25 (comment)
.

[paoloramos]

@voltagex : I actually found a workaround and posted it on SO => http://stackoverflow.com/questions/25529623/how-to-handle-delicious-api-authorize-redirect-not-handling-existing-url-get-par

I hope you find it useful.

[peoplemerge]

Should just need to urlencode the &code=a_code