Avatar for Username

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Jetty not working on firefox

ripusing
ripusing
more options

I have a .js file that is part of a web-application. The web application is deployed on tomcat. This .js file in turn calls a .html file deployed on jetty. This .html file is responsible for starting the cometd service, but when i run my web-app, firefox throws an abort message for this particular request. Also this is the first request that im sending to jetty.

Strangely enough, when i paste the URL of that particular .html file(or its parent servlet) on my address bar in a new session, the URL gets loaded and when i start my web-app, firefox throws a successful 200 on that page(on seeing from firebug).

This is a one client operation, this behaviour(of successful 200 on that page) persists for that particular client as long as firefox is not re-installed. Therefore, my web app loads that very page successfully for the client that has loaded that url explicitly from the address bar and I do not have to load that page from the address bar again till i do not re-install my browser.

Can anyone explain what information is passed to the client such that it stays for that client even on deleting temporary internet files/cookies/browser restart/system reboot but not on browser re-install?

Also, if possible, can anyone suggest a proper approach to follow so that i do not have to perform this work-around to get that page loaded on every client that uses my web-app?

I have a .js file that is part of a web-application. The web application is deployed on tomcat. This .js file in turn calls a .html file deployed on jetty. This .html file is responsible for starting the cometd service, but when i run my web-app, firefox throws an abort message for this particular request. Also this is the first request that im sending to jetty. Strangely enough, when i paste the URL of that particular .html file(or its parent servlet) on my address bar in a new session, the URL gets loaded and when i start my web-app, firefox throws a successful 200 on that page(on seeing from firebug). This is a one client operation, this behaviour(of successful 200 on that page) persists for that particular client as long as firefox is not re-installed. Therefore, my web app loads that very page successfully for the client that has loaded that url explicitly from the address bar and I do not have to load that page from the address bar again till i do not re-install my browser. Can anyone explain what information is passed to the client such that it stays for that client even on deleting temporary internet files/cookies/browser restart/system reboot but not on browser re-install? Also, if possible, can anyone suggest a proper approach to follow so that i do not have to perform this work-around to get that page loaded on every client that uses my web-app?

Toate răspunsurile (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

I'm curious what you mean about Firefox throwing an abort message. This is not a time-out or error from the server, but Firefox is itself terminating the request?

Is it a cross-domain request? Some users have discovered that offsite resources such as style sheets will not load until they have visited the server directly. This sounds like some kind of filtering, but in the threads I participated in, we didn't uncover the actual cause of it.