Angular 8 app works on Chrome returns 304 on Firefox and IExp
420 views
Skip to first unread message
w stafford
Sep 6, 2019, 2:32:13 PM9/6/19
to Angular and AngularJS discussion
I recently set up Angular 8 on a Windows 7 desktop. node 10.16.3 LTS, CLI 8.3.2, NPM 6.2.0
I followed this page of instructions: https://www.freecodecamp.org/news/how-to-get-up-and-running-with-angular-on-windows-7405ba745c25/
After sending the URL: localhost:4200 The sample app comes up on Chrome but not on Firefox or IExp.
On Firefox and IExp I get several 304 return codes and the index.html is displayed.
I sort of understand the 304, a header returned by the server indicates that the browser should use a cached copy of the resource.
However, this is a new installation. There should be no cached pages.Clearing the cache did not help. Even more puzzling, the files in the 304 msg are *.js files.
I thought a 304 always referenced images, not executable files.
The good news is the sample app is probably correct and all required files are in place and there are no version errors.
The bad news is I have no Idea what to try to make this thing work on other browsers.
I know this is probably not an Angular issue, in the sense that Angular code is incorrect.
However, only Angular developers are likely to see issue this so I'm hoping someone here has seen this and knows what to do.
Thanks for any leads,
-=b
I followed this page of instructions: https://www.freecodecamp.org/news/how-to-get-up-and-running-with-angular-on-windows-7405ba745c25/
After sending the URL: localhost:4200 The sample app comes up on Chrome but not on Firefox or IExp.
On Firefox and IExp I get several 304 return codes and the index.html is displayed.
I sort of understand the 304, a header returned by the server indicates that the browser should use a cached copy of the resource.
However, this is a new installation. There should be no cached pages.Clearing the cache did not help. Even more puzzling, the files in the 304 msg are *.js files.
I thought a 304 always referenced images, not executable files.
The good news is the sample app is probably correct and all required files are in place and there are no version errors.
The bad news is I have no Idea what to try to make this thing work on other browsers.
I know this is probably not an Angular issue, in the sense that Angular code is incorrect.
However, only Angular developers are likely to see issue this so I'm hoping someone here has seen this and knows what to do.
Thanks for any leads,
-=b
Sander Elias
Sep 10, 2019, 3:53:23 AM9/10/19
to Angular and AngularJS discussion
Hi W,
I have read the article, and it seems to take the right steps. (also, it would also fail on chrome if that was off)
So, for now, I’m assuming its nothing in the angular or dev-tools setup.
I do suspect you have something running already on your computer that is making the other browsers throw. Can you try in the other browsers with the ip 127.0.0.1:4200 instead of localhost?
Another thing you can try is to run the tools on a different port.
try ng serve -p 4123 and go to localhost:4123
Does that help?
Regards
Sander
w stafford
Sep 10, 2019, 3:30:52 PM9/10/19
to ang...@googlegroups.com
Sander,
Thanks for the reply. Unfortunately, no joy. Port number does not make a difference.--
You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to angular+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/angular/199645e0-c9a1-443e-93b0-84cc88688348%40googlegroups.com.
Sander Elias
Sep 10, 2019, 11:28:14 PM9/10/19
to Angular and AngularJS discussion
And using the IP instead?
Reply all
Reply to author
Forward
0 new messages