[jira] Closed: (SHINDIG-184) Incorrect placement of OAuth parameters

["Kevin Brown (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SHINDIG-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Brown closed SHINDIG-184.
-------------------------------

    Resolution: Fixed

Applied in r648154. Thanks!

> Incorrect placement of OAuth parameters
> ---------------------------------------
>
>                 Key: SHINDIG-184
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-184
>             Project: Shindig
>          Issue Type: Bug
>          Components: Gadget Rendering Server (Java)
>            Reporter: Dirk Balfanz
>         Attachments: patch-paramter-location.txt
>
>
> Currently, the OAuth code in shindig places the OAuth parameters insider the URL query part if the HTTP method is GET, and into the  POST body of the HTTP method is POST. This breaks when there is already a POST body that is not of type x-www-form-urlencoded. The attached patch fixes this issue, and introduces correct handling of OAuth parameter locations. There is now an (optional) parameter to the oauth feature in which a gadget developer can specify where the OAuth parameters should go - the default is the Authorization: header.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.