https://www.etc...... We initially had just a relative path in out client requests. I'll bet this isn't your problem. I only mentioned it because the symptoms were similar.
> On Dec 4, 2014, at 7:39 AM, Jörg Zimmer <[email protected]> wrote: > > Hi Jonathan, > > as the api is running on it's own domain, we sure have the full url path in > our request. > Or what exactly do you mean by "full" > > Joerg > > -- > You received this message because you are subscribed to a topic in the Google > Groups "AngularJS" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/angular/3hP4JpTHLYY/unsubscribe. > To unsubscribe from this group and all its topics, 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. -- 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.
