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

Erik BI commented on SHINDIG-1548:
----------------------------------

My pleasure, Henry ^_^
                
> Shindig does not accept relative URLs for template libraries
> ------------------------------------------------------------
>
>                 Key: SHINDIG-1548
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1548
>             Project: Shindig
>          Issue Type: Bug
>          Components: Java
>    Affects Versions: 2.0.2, 2.5.0-beta1
>            Reporter: Craig McClanahan
>            Assignee: Henry Saputra
>              Labels: patch
>             Fix For: 2.5.0
>
>         Attachments: 1548.patch, RelativeTemplateLibrary.xml, 
> TestTemplateLibrary.xml
>
>
> Section 15.1 of the OpenSocial Templating Spec (version 1.1 at 
> <http://opensocial-resources.googlecode.com/svn/spec/1.1/OpenSocial-Templating.xml#rfc.section.15.1>,
>  version 2.0 draft at 
> <http://opensocial-resources.googlecode.com/svn/spec/2.0/OpenSocial-Templating.xml#rfc.section.15.1>
>  states that, when interpreting the URL in a template library request like 
> this:
> {code}
> <Require feature="opensocial-templates">
>   <Param name="requireLibrary">templates.xml</Param>
> </Require>                                    
> {code}
> that "Relative URLs are interpreted in relation to the location of the Gadget 
> Spec XML file."  However, Shindig currently generates a /gadgets/makeRequest 
> call and passes in the relative URL value ("templates.xml") and fails with an 
> HTTP status of 400 (Bad Request) because this URL does not start with "http:" 
> or "https:".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to