[jira] Resolved: (SHINDIG-1328) relative URLs not supported in oauth service declaration

["Paul Lindner (JIRA)" <ji...@apache.org>]

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

Paul Lindner resolved SHINDIG-1328.
-----------------------------------

    Fix Version/s: 2.0.0-RC1
       Resolution: Fixed

> relative URLs not supported in oauth service declaration
> --------------------------------------------------------
>
>                 Key: SHINDIG-1328
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1328
>             Project: Shindig
>          Issue Type: Bug
>          Components: Java
>    Affects Versions: 1.0.1
>            Reporter: Randy Hudson
>             Fix For: 2.0.0-RC1
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> If a gadget contains the following:
> ...
> <Service name="my_service_name">
>      <Access url="../oauth-access-token" method="POST"/>
>     ....
> </Service>
> ...
> shindig will not properly resolve the URL.  In most other places, including /Module/Content/@href, /Module/ModulePrefs/@thumbnail, etc., URLs are all correctly resolved against the XML node's base URI.
> The OpenSocial Specification describes all of these attributes simply as being "URLs", so shindig is not following the specification consistently by inconsistently accepting relative value.
> For authors of gadget which get co-deployed along with some server instance, this means the gadget must be rewritten for each server instance on which it is deployed.
> The fix for this is trivial and recently described on the mailing list.

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