Sending this again.... not sure why it didn't work the first time. Sorry if you get a duplicate.... -----------------------------------------------------------------------------------------------------------------------------------
Hi John, No, I'm using the DefaultUriParser. It's odd because if I step through the code and change the value of "host" at runtime in the debugger to be prefixed by "http://"; before the parse, then it works. The error is coming from org.apache.shindig.common.uri.Uri.fromJavaUri(). I'm hitting the "No support for opaque Uris" error. Looking at the java.net.URI documentation, this makes sense as to why it thinks this url is opaque, but I don't understand how this ever worked for absolute urls without overriding the default implementations since we never set the scheme for the uri. Any ideas? Thanks, -Stanton From: John Hjelmstad <[email protected]> To: [email protected], Cc: Stanton Sievers/Westford/IBM@Lotus Date: 03/31/2011 19:19 Subject: Re: DefaultIframeUriManager for locked domains Hi Stanton, Odd, this has worked for us for quite some time. Uri.parse(...) just doesn't throw a UriException. Are you overriding UriParser? On Thu, Mar 31, 2011 at 2:57 PM, Stanton Sievers <[email protected]>wrote: > Hi, > > Has anyone been able to use the DefaultIframeUriManager when locked > domains are configured? I've configured > gadgets.uri.iframe.lockedDomainSuffix in my container.js and have set > shindig.locked-domain.enabled=true in shindig.properties. I seem to be > hitting the correct code paths, but I think the logic in > DefaultIframeUriManager.makeRenderingUri() is incorrect. > > In the case where locked domains are enabled we do a string concatenation > of the generated locked domain prefix and the configured > gadgets.uri.iframe.lockedDomainSuffix in order to build the host name. The > problem is that immediately after that we try to do Uri.parse() on the > host name which is throwing a UriException because we don't have a > protocol/schema for the url, i.e., the url is just <gadget url > hash>.mydomain.com instead of http://<gadget url hash>.mydomain.com. > > Does this just not work for the DefaultIframeUriManager and those who want > locked domains need to bind to their own UriModule? > > Thanks, > -Stanton > >
