[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 131
  • Last Modified:

website issue in Firefox

A website that I have working on my local machine inside both  IE and Chrome does not work in Firefox 49.0.2.

The site is under development and is not accessible to the public yet so I cannot provide a link.  For now I am focusing on browser configuration issues, as changing those in IE and Chrome has apparently helped.  But the same changes in Firefox do not seem to make any difference (allowing cookies).

I ran the Dev Tools and looked at the console log:

TokenManager.redirectForToken error: Network error)oidc-token-manager.min.js:4:1777
a.prototype.redirectForToken/<()oidc-token-manager.min.js:4

Error: Network error)oidc-token-manager.min.js:2:1422

Not sure how to fix this problem.
0
Tom Knowlton
Asked:
Tom Knowlton
  • 5
  • 2
2 Solutions
 
Jackie ManCommented:
IE and Chrome works?
0
 
Tom KnowltonWeb developerAuthor Commented:
IE and Chrome works?

That is correct.
0
 
shalomcCTOCommented:
Hard to diagnose without access to the source code, but lets try.
You test the pages locally. Does it mean that you don't have a local web server? This looks like an error related to Angular, which means that you have some AJAX calls, and browsers do not in general like to do AJAX from local files.
Try to run a local instance of Apache/IIS/whatever web server you can and see if that help.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Tom KnowltonWeb developerAuthor Commented:
Try to run a local instance of Apache/IIS/whatever web server you can and see if that help.

Up to this point I've been running "nodemon".

It makes no difference in the problem.
0
 
shalomcCTOCommented:
Nodemon has nothing to do with it, but my answer was not 100% clear.
So just in case you did not do it yet - Start a local web server, put your html app on it, and access it via http://localhost/something..  rather than file://something..

And don't forget CORS headers, too.
0
 
Tom KnowltonWeb developerAuthor Commented:
To my knowledge I've never tried to access the web application via file:// I've always had the web server serve-it-up.

What is a CORS Header?
0
 
Tom KnowltonWeb developerAuthor Commented:
So CORS = Cross Origin Resource Sharing.

But why would Chrome and IE be okay and Firefox would need CORS?
0
 
Tom KnowltonWeb developerAuthor Commented:
It turned-out to be a certificate issue.
0

Featured Post

Take Control of Web Hosting For Your Clients

As a web developer or IT admin, successfully managing multiple client accounts can be challenging. In this webinar we will look at the tools provided by Media Temple and Plesk to make managing your clients’ hosting easier.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now