You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Stanton Sievers (JIRA)" <ji...@apache.org> on 2013/09/10 19:17:51 UTC
[jira] [Updated] (SHINDIG-1933) Flash RPC transport does not setup
properly
[ https://issues.apache.org/jira/browse/SHINDIG-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stanton Sievers updated SHINDIG-1933:
-------------------------------------
Description:
Steps to reproduce:
1) Configure an unlocked domain in container.js, i.e, set real hostname values for "default.domain.unlocked.client" and "default.domain.unlocked.server". For example, use "unlocked.shindig.com" and set it to 127.0.0.1 in your hosts file.
2) Navigate to the common container page and force it to use the flash RPC transport by using the query param: http://localhost:8080/containers/commoncontainer/index.html?rpctx=flash
3) Load the "Publish Suscribe Demo" set of gadgets
Expected result: The gadgets render and function
Actual result: The gadgets do not render
If you then remove the "rpctx=flash" query param, the gadgets will work.
Note: You must have the gadget domain be different than the container domain, or RPC simply short-circuits and makes calls directly instead of relying on the rpc transports.
was:
Steps to reproduce:
1) Configure an unlocked domain in container.js, i.e, set real hostname values for "default.domain.unlocked.client" and "default.domain.unlocked.server". I'll use "unlocked.shindig.com" for the rest of this example.
2) Navigate to the common container page and force it to use the flash RPC transport by using the query param: http://localhost:8080/containers/commoncontainer/index.html?rpctx=flash
3) Load the "Publish Suscribe Demo" set of gadgets
Expected result: The gadgets render and function
Actual result: The gadgets do not render
If you then remove the "rpctx=flash" query param, the gadgets will work.
Note: You must have the gadget domain be different than the container domain, or RPC simply short-circuits and makes calls directly instead of relying on the rpc transports.
> Flash RPC transport does not setup properly
> -------------------------------------------
>
> Key: SHINDIG-1933
> URL: https://issues.apache.org/jira/browse/SHINDIG-1933
> Project: Shindig
> Issue Type: Bug
> Components: Javascript
> Affects Versions: 2.5.1
> Environment: Windows 7 64-bit
> Firefox 23.0.1
> Reporter: Stanton Sievers
> Labels: flash, rpc
>
> Steps to reproduce:
> 1) Configure an unlocked domain in container.js, i.e, set real hostname values for "default.domain.unlocked.client" and "default.domain.unlocked.server". For example, use "unlocked.shindig.com" and set it to 127.0.0.1 in your hosts file.
> 2) Navigate to the common container page and force it to use the flash RPC transport by using the query param: http://localhost:8080/containers/commoncontainer/index.html?rpctx=flash
> 3) Load the "Publish Suscribe Demo" set of gadgets
> Expected result: The gadgets render and function
> Actual result: The gadgets do not render
> If you then remove the "rpctx=flash" query param, the gadgets will work.
> Note: You must have the gadget domain be different than the container domain, or RPC simply short-circuits and makes calls directly instead of relying on the rpc transports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira