I had exactly the same problem as Louis, but since Chrome 48 all the CORS extensions seem to have stopped working. I've come up with an alternative solution which I thought I'd share.
- In your Chrome installation directory - probably C:Program Files (x86)GoogleChromeApplication - create a shortcut to the chrome.exe
- Right click on this shortcut and select Properties
- On the Shortcut tab, in the Target field append the following two fields --allow-file-access-from-files --disable-web-security
4 . Save this and rename the shortcut to "Google Chrome - Debug with Ripple"
- Right click on it and select Pin to Start Menu
This shortcut will allow you to run Chrome with no web security, which allows CORS in Ripple. By using a shortcut this will not interfere with your normal use of Chrome. Now in order to use Ripple
- In Visual Studio debug your app which will start Ripple in its own Chrome instance
- Now open the start menu and click on the pinned "Google Chrome - Debug with Ripple" shortcut
- A second instance of Chrome will launch with a warning of "You are using an unsupported command-line flag: -- disable-web-security. Stability and security will suffer."
- Copy the Ripple proxy URL from the Visual Studio instance to this new one, for example http://localhost:4400/index.html?enableripple=cordova-3.0.0-NexusS
- Your CORS requests will now work in Ripple.
Note that Visual Studio has just been used to launch Ripple. Debugging will need to take place using Chrome's Developer Tools.
Note also that you can double check that Chrome is using your shortcut flags by browsing to the url chrome://version/
Hope this helps!
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…