[jira] Commented: (SHINDIG-183) OAuth for JSON targets is broken

["Brian Eaton (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SHINDIG-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586621#action_12586621 ] 

Brian Eaton commented on SHINDIG-183:
-------------------------------------

Erm.  Hard to tell from looking at a patch file, but it looks like this will leave bad indentation in the file.  Can you fix the indentation?

> OAuth for JSON targets is broken
> --------------------------------
>
>                 Key: SHINDIG-183
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-183
>             Project: Shindig
>          Issue Type: Bug
>          Components: Gadgets Server - Java
>            Reporter: Dirk Balfanz
>         Attachments: patch-empty-json-response.txt
>
>
> Currently, OAuth for JSON targets is broken. When a Gadget does a makeRequest with ContentType.JSON and AuthorizationType.AUTHENTICATED (i.e. OAuth), then typically the first roundtrip between shindig and the makeRequest target is an OAuth call to obtain a request token. The response text at that point will be empty. Which currently causes a "text has no properties" error when the response handler tries to parse the received JSON, and breaks the OAuth flow.
> The attached patch fixes the issue by allowing JSON responses that have an empty body.

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