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 are the network requests.

beta1

http://localhost:8080/gadgets/js/container:rpc.js?nocache=1&c=1&debug=1&cont
ainer=oclc

http://localhost:8080/gadgets/ifr?url=http%3A%2F%2Flocalhost%3A8080%2Fsample
container%2Fexamples%2FSocialHelloWorld.xml&container=oclc&view=default&lang
=%25lang%25&country=%25country%25&debug=0&nocache=0&sanitize=%25sanitize%25&
v=eebb355586ff23b9c618f7fa8ff88886&st=-1%3A-1%3Ahttp%253A%252F%252Flocalhost
%253A8080%252Fsamplecontainer%252Fexamples%252FSocialHelloWorld.xml%3A*%3Aht
tp%253A%252F%252Flocalhost%253A8080%252Fsamplecontainer%252Fexamples%252FSoc
ialHelloWorld.xml%3A0%3Aoclc%3A1339098219&testmode=0&parent=http%3A%2F%2Floc
alhost%3A8080&mid=0

beta2

http://localhost:8080/gadgets/js/container:rpc.js?nocache=1&c=1&debug=1&cont
ainer=oclc

http://localhost:8080/gadgets/ifr?url=http%3A%2F%2Flocalhost%3A8080%2Fsample
container%2Fexamples%2FSocialHelloWorld.xml&container=default&view=default&l
ang=en&country=US&debug=0&nocache=0&sanitize=%25sanitize%25&v=d5ef46b167d11a
be9a1962131163d6f5&st=-1%3A-1%3Ahttp%253A%252F%252Flocalhost%253A8080%252Fsa
mplecontainer%252Fexamples%252FSocialHelloWorld.xml%3A*%3Ahttp%253A%252F%252
Flocalhost%253A8080%252Fsamplecontainer%252Fexamples%252FSocialHelloWorld.xm
l%3A0%3Adefault%3A1339097193&testmode=0&parent=http%3A%2F%2Flocalhost%3A8080
&mid=0#rpctoken=97245479

In order to test this you need to modify your container.js file as follows

{"gadgets.container" : ["default", "accel", "oclc"]

(or I guess you could just try accel).

I'll keep poking around and try to figure out what set of changes caused
this.  Perhaps a unit test for testing this failure is in order.

Is this major enough to hold up beta2?  It's a big deal for us because we
use a different container to override some of the behavior of the default
container.

doug

On 6/7/12 1:35 PM, "Henry Saputra" <henry.sapu...@gmail.com> wrote:

> 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 <davi...@oclc.org> wrote:
>> 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/opensocial/gadgets/ifr?url=https%3A%2F%2Fw
>> orldkat.qa.oclc.org%2Fgallery%2Fgadgets%2F40%2Fxml&container=oclc&view=defau
>> lt&lang=en&country=US&debug=0&nocache=1&sanitize=0&v=584fb331f9d4272d7164ccf
>> e49e0569c&st=oclc%3ATOKEN&testmode=0&parent=http%3A%2F%2Focwms.worldkat.qa.o
>> clc.org&mid=0
>> 
>> Notice that the container is CORRECT (oclc). ?For length purpose I did not
>> show the entire length of our security token (it¹s long) so I just put
>> TOKEN.
>> 
>> In beta2 I see
>> 
>> http://platform.oclc.org:8080/opensocial/gadgets/ifr?url=http%3A%2F%2Fplatfo
>> rm.oclc.org%3A8080%2Fopensocial-demo%2Fgadgets%2Fsettitle.xml&container=defa
>> ult&view=default&lang=en&country=US&debug=0&nocache=0&sanitize=0&v=1545d7ce1
>> 25d3b0f296d91751cbba444&st=%25st%25&testmode=0&parent=http%3A%2F%2Fplatform.
>> oclc.org%3A8080&mid=0#rpctoken=147042121
>> 
>> Notice the container is WRONG (default) and that the ST param is null
>> because when it went to lookup the crypter for the container it was not
>> found (I¹m not sure why default isn¹t found... Still checking on that). ?If
>> I hardcode OCLC at
>> 
>> ? ?BlobCrypter crypter = crypters.get(aToken.getContainer());
>> 
>> In BlobCrypterSecurityTokenCodec when it does the crypter lookup then
>> everything works fine.
>> 
>> Does anyone have any ideas what may have changed and where to look?
>> 
>> doug
>> 
> 


Reply via email to