Hi Almost certain it's cors... We have to support a number of routers - most still have an 80's interface to authorise users. They're unlikely to change and even if they did, the volume on old firmwares would still be too high.
We have our own routers with JSON interface which makes things easy. I wasn't aware you could proxy on the server. Is something like this what you mean: https://github.com/gr2m/CORS-Proxy It's workable our side but the captive portal app is open-source and we're trying to make it super easy for people to integrate. Thank you for the other references, I will dig into xmhhttprequest now. S On Thursday, 22 January 2015 06:32:10 UTC, Sander Elias wrote: > > Hi Simon, > > As said in other answers you are running into a CORS issue, and this > should be solved on the router itself. If that's not possible, you need a > proxy indeed. I assume you have access to the server your app is hosted on? > You can add the proxy function to that server, and be done with it. just > let your server do the request to the router, and send the needed results > off the the client, there are no CORS issues that way. > > Also, you are running in a browser. $http is NOT the only way you can > communicate with the outside world. Its the most convenient, but > definitively not the only way. You can use xmhhttprequest directly, or use > another library. > > Regards > Sander > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
