[SHINDIG-1884] open social feature config path hardcoded the http scheme

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.0-beta5
• Fix Version/s: 2.5.0, 2.5.0-beta6
• Component/s: Javascript
• Assignee: Unassigned
• Reporter: Marshall Shi
• Created: 28/Nov/12 13:39
• Updated: 31/Jan/13 02:43
• Resolved: 26/Dec/12 15:18

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.

Issue Links

• relates to: SHINDIG-1870 Cross-site issue as http scheme is hardcoded in some URI template in container.js