On Wed, Nov 5, 2014 at 11:06 PM, Sander Elias <[email protected]> wrote: > You can do what you need, by setting the correct headers, and support OPTION > requests at your server side. > In some cases adding the header `Access-Control-Allow-Origin: *` will be > enough. Often it will not be. > Here is a flowchart, of what your server needs to take care off.
I've had some success using xdomain* with Angular - it's not really CORS, but rather an alternative that accomplishes mostly the same and is considerably easier to work with. (That said, I've not conducted a security audit against it as yet ) <https://github.com/jpillora/xdomain> Best, -- Scott Elcomb @psema4 http://psema4.com/pubkey.txt http://www.pirateparty.ca/ -- 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.
