ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brent Lintner (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (RIPPLE-63) Ripple should default to local proxy, not remote
Date Sun, 16 Nov 2014 19:36:33 GMT

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

Brent Lintner resolved RIPPLE-63.
---------------------------------
    Resolution: Fixed

Fixed with: https://github.com/apache/incubator-ripple/pull/35

> 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)

Mime
View raw message