You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Erik Serating (JIRA)" <ji...@apache.org> on 2010/09/15 19:15:33 UTC
[jira] Created: (SHINDIG-1427) Cannot use relative url for proxy or
concat path
Cannot use relative url for proxy or concat path
------------------------------------------------
Key: SHINDIG-1427
URL: https://issues.apache.org/jira/browse/SHINDIG-1427
Project: Shindig
Issue Type: Bug
Components: Java
Affects Versions: 2.0.0
Environment: windows
Reporter: Erik Serating
In shindig beta 1.3 you could use a relative or context path such as "/cm/gadgets/proxy" and it would work fine. In shindig 2.0.0 this can not be done.
I use the following 2 entries in my container.js file hoping the relative context path will work:
"gadgets.uri.concat.host" : "",
"gadgets.uri.concat.path" : "/cm/gadgets/concat",
"gadgets.uri.proxy.host" : "",
"gadgets.uri.proxy.path" : "/cm/gadgets/proxy",
What happens is that 2 forward slash are always added to the beginning of the urls that shindig generates so that the above paths become:
///cm/gadget/concat
///cm/gadget/proxy
There should be away to config whether or not the // should be used as a url prefix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-1427) Cannot use relative url for proxy
or concat path
Posted by "Murali VP (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912241#action_12912241 ]
Murali VP commented on SHINDIG-1427:
------------------------------------
One fix could be:
Make specifying of host optional in container.js. DefaultConcatUri.getReqVal(String container, String key) throws RuntimeException if value of key (eg. "gadgets.uri.concat.host") is not specified. Change it to have it return null for optional keys. Additionally DefaultConcatUri.makeConcatUri() should also check for empty CONCAT_HOST_PARAM value.
Uri.Uri(UriBuilder builder) prepends a '//' only if authority is non-null.
> Cannot use relative url for proxy or concat path
> ------------------------------------------------
>
> Key: SHINDIG-1427
> URL: https://issues.apache.org/jira/browse/SHINDIG-1427
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 2.0.0
> Environment: windows
> Reporter: Erik Serating
>
> In shindig beta 1.3 you could use a relative or context path such as "/cm/gadgets/proxy" and it would work fine. In shindig 2.0.0 this can not be done.
> I use the following 2 entries in my container.js file hoping the relative context path will work:
> "gadgets.uri.concat.host" : "",
> "gadgets.uri.concat.path" : "/cm/gadgets/concat",
> "gadgets.uri.proxy.host" : "",
> "gadgets.uri.proxy.path" : "/cm/gadgets/proxy",
> What happens is that 2 forward slash are always added to the beginning of the urls that shindig generates so that the above paths become:
> ///cm/gadget/concat
> ///cm/gadget/proxy
> There should be away to config whether or not the // should be used as a url prefix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.