You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Marshall Shi (JIRA)" <ji...@apache.org> on 2012/12/04 02:45:58 UTC
[jira] [Updated] (SHINDIG-1884) open social feature config path
hardcoded the http scheme
[ https://issues.apache.org/jira/browse/SHINDIG-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Shi updated SHINDIG-1884:
----------------------------------
Description:
Default container.js has such setting for open social feature:
"opensocial" : {
// Path to fetch opensocial data from
// Must be on the same domain as the gadget rendering server
"path" : "http://%host%${CONTEXT_ROOT}/rpc",
// Path to issue invalidate calls
"invalidatePath" : "http://%host%${CONTEXT_ROOT}/rpc",
Problem with these setting is that if consumer deploy Shindig with HTTPS, they need to manually change the http here to https. Proposal is to leave the scheme part of the setting empty and request send will be automatically use the relative scheme.
was:
Default container.js has such setting for open social feature:
"opensocial" : {
// Path to fetch opensocial data from
// Must be on the same domain as the gadget rendering server
"path" : "http://%host%${CONTEXT_ROOT}/rpc",
// Path to issue invalidate calls
"invalidatePath" : "http://%host%${CONTEXT_ROOT}/rpc",
Problem with these setting is that if consumer deploy Shindig with HTTPS, they need to manually change the http here to https. Proposal is to leave the scheme part of the setting empty and construct the full path in the js code.
> open social feature config path hardcoded the http scheme
> ---------------------------------------------------------
>
> Key: SHINDIG-1884
> URL: https://issues.apache.org/jira/browse/SHINDIG-1884
> Project: Shindig
> Issue Type: Bug
> Components: Javascript
> Affects Versions: 2.5.0-beta5
> Reporter: Marshall Shi
> Fix For: 2.5.0-beta5
>
> Attachments: opensocial_path.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Default container.js has such setting for open social feature:
> "opensocial" : {
> // Path to fetch opensocial data from
> // Must be on the same domain as the gadget rendering server
> "path" : "http://%host%${CONTEXT_ROOT}/rpc",
> // Path to issue invalidate calls
> "invalidatePath" : "http://%host%${CONTEXT_ROOT}/rpc",
> Problem with these setting is that if consumer deploy Shindig with HTTPS, they need to manually change the http here to https. Proposal is to leave the scheme part of the setting empty and request send will be automatically use the relative scheme.
--
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