You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ripple.apache.org by "Brent Lintner (JIRA)" <ji...@apache.org> on 2015/02/17 23:05:12 UTC
[jira] [Closed] (RIPPLE-63) Ripple should default to local proxy,
not remote
[ https://issues.apache.org/jira/browse/RIPPLE-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brent Lintner closed RIPPLE-63.
-------------------------------
> Ripple should default to local proxy, not remote
> ------------------------------------------------
>
> Key: RIPPLE-63
> URL: https://issues.apache.org/jira/browse/RIPPLE-63
> Project: Apache Ripple
> Issue Type: Bug
> Reporter: Vladimir Kotikov
> Attachments: x-domain-proxy-default-brocken.png, x-domain-proxy-default-fixed.png, x-domain-proxy-local.png, x-domain-proxy-remote.png
>
>
> The default Ripple option is to use a remote proxy, so all calls go through e.g. https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippos_rurl=https%3A//login.somehost.net/common/oauth2/token.
> This is a terrible option because the information that user is sending may be extremely security sensitive.
> You can set the proxy to be local, but you’d need to specify that every time you launch Chrome.
> Using local proxy is more common practice, and maybe it should be used by default?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)