[
https://issues.apache.org/jira/browse/RIPPLE-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated RIPPLE-63:
-----------------------------------
Description:
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 tht 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?
was:
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 tht 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.
> 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
>
> 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 tht 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.2#6252)
