shindig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanton Sievers" <>
Subject Re: Review Request: Add test gadget to the common container sample to test domain configuration
Date Tue, 03 Jan 2012 15:18:36 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated 2012-01-03 15:18:36.205998)

Review request for shindig and Jasvir Nagra.


Added license boilerplate to the gadget.  Added Jasvir for his input.


This is the first of a couple of gadgets I'd like to commit that can act as unit tests for
testing deployment configurations, such as locked domains and security token encryption. 

This particular gadget simply tries to get at container information (the location) from within
the gadget.  In a properly configured environment this should be disallowed due to browser
same-origin policy.

Can anyone else think of anything that this gadget should be testing?  Currently it will simply
try to get at the parent window's location and then will keep lowering its domain to try to
match that of the container's.  

Diffs (updated)



Container: localhost, Gadget: localhost, Result: Fail
Container:, Gadget:, Result: Success
Container:, Gadget:, Result: Fail (when the container page has
set document.domain to location.hostname)

And I'm sure I tried some other things as well. :)



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message