Could you try to modify your container file to set
"osapi" : {
// The endpoints to query for available JSONRPC/REST services
"endPoints" : [ "//%host%${CONTEXT_ROOT}/rpc" ]
}
to point to shindighost.com?
- Henry
On Tue, Jul 31, 2012 at 10:52 AM, daviesd <[email protected]> wrote:
> They don't live on different hosts, they are just gotten there by different
> dns. For example the javascript request looks like:
>
> https://prefix.shindighost.com/gadgets/js/rpc.js?nocache=1&c=1&container=def
> ault
>
> However the server shouldn't go through prefix.shindighost.com. I really
> want it to go to shindighost.com.
>
> Sounds like I don't want it to use the "host" header but instead set
> shindig.host appropriately. Especially since the authority is used by other
> things like the oauth callbacks.
>
> doug
>
>
> On 7/31/12 12:57 PM, "Henry Saputra" <[email protected]> wrote:
>
>> Looks like the rpc call to system.listMethods is called in
>> RenderingGadgetRewriter and ConfigInjectionProcessor to execute the
>> gadgets.config.init
>>
>> For both scenario looks t will try to call itself using the request
>> "host" header.
>>
>> Doug, so in your setup the js serving endpoint live in different host
>> than the rpc endpoints?
>>
>> - Henry
>>
>> On Tue, Jul 31, 2012 at 8:03 AM, daviesd <[email protected]> wrote:
>>> I just recently noticed a behavior with the rpc interface that I have
>>> discovered in the 11th hour and we are ready to rollout, so any input asap
>>> is appreciated.
>>>
>>> Shindig at some point makes an rpc call back to itself for listMethods. I
>>> thought this use to happen upon startup, but I might be wrong. What appears
>>> to be happening is that it does this on the first request for the shindig
>>> javascript. And if you don¹t have a shindig host configured it appears to
>>> use the dns/host name from the request.
>>>
>>> Unfortunately in my environment that initial javascript goes to a different
>>> dns/host name than what I want my shindig server to use. I still don¹t
>>> understand why the shindig call doesn¹t use localhost (or just call
>>> internally to itself).
>>>
>>> Is just configuring shindig.host going to be enough to get around this
>>> problem?
>>>
>>> Thanks,
>>> doug
>>
>
>
