You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Kevin Brown (JIRA)" <ji...@apache.org> on 2008/03/06 08:53:58 UTC

[jira] Closed: (SHINDIG-108) Allow rpc feature to handle empty config.rpc.parentRelayUrl. Needed to support open containers

     [ https://issues.apache.org/jira/browse/SHINDIG-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Brown closed SHINDIG-108.
-------------------------------

    Resolution: Won't Fix

Closing this for now, but we may open up a somewhat related discussion soon, depending on what the results of some security-related discussions going on between myself, zhen, and brian eaton turn up. I think we may have a viable solution to deal with this special case, but it requires some more eyes to look at it. The actual proposed solution here isn't secure.

> Allow rpc feature to handle empty config.rpc.parentRelayUrl. Needed to support open containers
> ----------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-108
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-108
>             Project: Shindig
>          Issue Type: New Feature
>          Components: Features
>            Reporter: Sami Shalabi
>            Assignee: Kevin Brown
>         Attachments: rpc.patch
>
>
> Kevin suggested I set config.rpc.parentRelayUrl to "" to support gadget containers running on arbitrary websites while allowing for rpc to function. This required removing a validator in rpc.js

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.