Marshall Shi created SHINDIG-1884:
-------------------------------------
Summary: 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
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.
--
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
