Open jengee opened 12 years ago
This issue has been confirmed on Mac Lion and Win7-64
This issue is probably present for any local url. i.e. http://localhost (on any port) and http:127.0.0.1 (on any port)
Different behaviours when placing localhost and localhost:9900 in the list of exceptions if you have proxy settings
WinXP:
Chrome is able to access both websites localhost and localhost:9900 Ripple is unable to access both localhost and localhost:9900
Win7-64: Chrome is able to access both websites localhost and localhost:9900 Ripple is unable to access both localhost and localhost:9900
Mac Lion:
Chrome is able to access localhost websites but unable to connect localhost:9900 Ripple is unable to access both localhost and localhost:9900
If proxy settings are enabled on their machine, Ripple is unable to communicate with localhost:9900 or even localhost (webserver) for any of the local widgets installed on their machine.
This is seen on Snow Leopard and WinXP.
The scenario: On a WinXP machine, even though you have installed a webserver (ie tomcat), Chrome will still try to access the local webpage through the Proxy server.
For Ripple, (with proxy settings on) http://localhost/HelloWorld/index.html will never be loaded regardless of whether you have provided the proxy credentials or not.
The only way to access any local files on Ripple is to turn off Proxy server settings completely.