t; to the tag and rebuild the artifacts?
>
>
> -Ryan
>
>
>
>
> From:Stanton Sievers/Westford/IBM@Lotus
> To:dev@shindig.apache.org,
> Date: 06/07/2012 07:08 PM
> Subject: Re: Issue with container and security tokens in beta2
>
te it? Or should I port the
fix
> to the tag and rebuild the artifacts?
>
>
> -Ryan
>
>
>
>
> From: Stanton Sievers/Westford/IBM@Lotus
> To: dev@shindig.apache.org,
> Date: 06/07/2012 07:08 PM
> Subject: Re: Issue with container and security t
he fix
> to the tag and rebuild the artifacts?
>
>
> -Ryan
>
>
>
>
> From: Stanton Sievers/Westford/IBM@Lotus
> To: dev@shindig.apache.org,
> Date: 06/07/2012 07:08 PM
> Subject: Re: Issue with container and security tokens in beta2
>
&
dev@shindig.apache.org,
Date: 06/07/2012 17:55
Subject: Re: Issue with container and security tokens in beta2
Sweet =)
Yeah Ryan needs to create new RC for beta2 release (sorry Ryan)
- Henry
On Thu, Jun 7, 2012 at 2:11 PM, Stanton Sievers
wrote:
> Not if I assign it to
e.org,
Date: 06/07/2012 17:55
Subject: Re: Issue with container and security tokens in beta2
Sweet =)
Yeah Ryan needs to create new RC for beta2 release (sorry Ryan)
- Henry
On Thu, Jun 7, 2012 at 2:11 PM, Stanton Sievers
wrote:
> Not if I assign it to me first! :)
>
> Doug
only tag for beta2, not branch, right?
>
> Thanks,
> -Stanton
>
>
>
> From: Henry Saputra
> To: dev@shindig.apache.org,
> Date: 06/07/2012 16:55
> Subject: Re: Issue with container and security tokens in beta2
>
>
>
> Thanks Stanton, can I a
:Re: Issue with container and security tokens in beta2
Thanks Stanton, can I assign this to you?
- Henry
On Thu, Jun 7, 2012 at 1:45 PM, Stanton Sievers
wrote:
> I updated Doug's JIRA [1] with what I think the code needs to be changed
> to. I haven't tested it, howeve
HINDIG-1794
>
> Thanks,
> -Stanton
>
>
>
> From: Henry Saputra
> To: dev@shindig.apache.org,
> Date: 06/07/2012 16:31
> Subject: Re: Issue with container and security tokens in beta2
>
>
>
> Thanks Doug, looks like this check is not right !scriptEls
;debug=1&container=oclc
>> ");
>>
>> Doug, can you ensure that your tokens have the correct container in
them?
>>
>> Thanks,
>> -Stanton
>>
>>
>>
>>
>> From: Henry Saputra
>> To: dev@shindig.apache.org,
>&
one other thought. Do you have any other script tags
>> that match this regex in your page, Doug? We might be finding the wrong
>> one that doesn't have the container query param on it.
>>
>> Thanks,
>> -Stanton
>>
>>
>>
>> From: Stanton
evers/Westford/IBM
> To: dev@shindig.apache.org,
> Date: 06/07/2012 15:15
> Subject:Re: Issue with container and security tokens in beta2
>
>
> Henry,
>
> I think it does match. I executed the folllowing in my firebug console
> and it
e.org,
Date: 06/07/2012 15:15
Subject: Re: Issue with container and security tokens in beta2
Henry,
I think it does match. I executed the folllowing in my firebug console
and it returned true:
/.*gadgets\/js\/.*container.*[.]js.*[?&]c=1(&|$).*/.test("
http://ocwms.wo
quot;);
>
> Doug, can you ensure that your tokens have the correct container in them?
>
> Thanks,
> -Stanton
>
>
>
> From: Henry Saputra
> To: dev@shindig.apache.org,
> Date: 06/07/2012 14:55
> Subject:Re: Issue with container and security
;container=oclc
");
Doug, can you ensure that your tokens have the correct container in them?
Thanks,
-Stanton
From: Henry Saputra
To: dev@shindig.apache.org,
Date: 06/07/2012 14:55
Subject: Re: Issue with container and security tokens in beta2
Actually its
Actually its maybe in the init.js function initializeGlobalVars()
Looks like the URL
http://ocwms.worldkat.qa.oclc.org/opensocial/gadgets/js/oclccontainer:userpr
efsui:rpc.js?nocache=1&c=1&debug=1&container=oclc does not contain the
expected pattern
/.*gadgets\/js\/.*container.*[.]js.*[?&]c=1(&|$
Henry/All,
I retested with snapshots of beta1 and beta2 (ruling out all my extensions
in our container).
There is definitely a difference in behavior. In beta1 buildUri gets the
container name right (oclc).
String container = context.getContainer();
In beta2 in gets it wrong (default).
Here a
Seems like the iframe URL returned from the metadata call gets the
wrong container.
Doug, could you debug in the DefaultIframeUriManager.buildUri what is
the container returned?
- Henry
On Thu, Jun 7, 2012 at 9:30 AM, daviesd wrote:
> In beta1 I use to see the following flow.
>
> Request the ja
In beta1 I use to see the following flow.
Request the javascript using container=oclc
http://ocwms.worldkat.qa.oclc.org/opensocial/gadgets/js/oclccontainer:userpr
efsui:rpc.js?nocache=1&c=1&debug=1&container=oclc
The iframe request would then look as follows
http://ocwms.worldkat.qa.oclc.org/op
18 matches
Mail list logo
