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 > >
