A GET request is fairly easy to verify: 1. You can copy and paste the full url directly into the address bar. 2. If you are on Linux or Mac, you can use cURL (or wget) on the command line and see if it's getting there. 3. Worst case you can use WireShark to inspect network packets.
Sounds to me like the server just isnt responding, but you would know if you can verify the server logs (apache?). Anyway, point is, it is a "guess" that it's firewall or chrome plugin until you can verify it works outside of the web page and angular. On Tuesday, February 11, 2014 2:14:21 PM UTC-7, Kevin Shay wrote: > > On Tue, Feb 11, 2014 at 3:36 PM, Jeffery Swensen > <[email protected]<javascript:> > > wrote: > >> What would cause an ngResource GET request to not reach the server? >> >> The request is listed as Pending in Chrome Dev Tools and no matter how >> long I wait, the server never actually receives the request. >> > > > Some Chrome plugins (e,g. ad blockers) and firewall/antivirus software can > cause this behavior. > > If the request is making it to the Network pane, it doesn't seem like an > Angular-specific issue. > > Kevin > -- 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/groups/opt_out.
