oauth_callback not respected when passed via headers

[jesseditson]

Hey there!

I was trying to authorize using an Authorization header, and while I am successfully able to hit the request_token endpoint and authorize endpoint, after I authorize the app I'm taken to the default_callback page instead of redirecting to the endpoint specified when passing an oauth_callback param via the Authorization header to the request_token endpoint.

I was successfully able to perform the same transaction using a POST, so I suspect that this may be an edge case on your side.

[alangpierce]

Hi, thanks for the report. Agreed that this is a bug. I filed an internal issue, although we're treating it as pretty low priority for now because of the POST workaround. I can raise the priority if this becomes more of an annoyance, though.

[jesseditson]

No worries,  I've worked around it in my end so no hurry. 

—
Sent from Mailbox

On Sat, Sep 19, 2015 at 6:40 PM, Alan Pierce [email protected]
wrote:

Hi, thanks for the report. Agreed that this is a bug. I filed an internal issue, although we're treating it as pretty low priority for now because of the POST workaround. I can raise the priority if this becomes more of an annoyance, though.

Reply to this email directly or view it on GitHub:
#95 (comment)