Looks like it needs code fix. Maybe we could use the client side shindig.uri feature to construct the right URL
- Henry On Mon, Feb 6, 2012 at 3:09 PM, Li Xu <[email protected]> wrote: > Stanton, > Doesn't seem like it can workaround without a fix this time...Here's what I > think how we may fix this: > > cfg[osapi.container.ServiceConfig.PROXY_URI] = "http://localhost:8181/proxy > "; > cfg[osapi.container.ServiceConfig.API_HOST] = "http://localhost:8080/cre";; > cfg[osapi.container.ServiceConfig.API_PATH] = "rpc"; > > When adding the st information in jsonrpctransport.js: > url +="?st="; ==> this would be API_HOST+API_PATH+"?st" > url += encodeURIComponent(token); > > now we need to check if proxy url is available and shindig API_HOST is a > cross domain url for current site, > it would have to encode the whole url portion in above example, then append > it back as a url parameter to proxy url like... > > any comments? > > thanks, > li
