This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

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.

Learn More

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

Race Cache With Network

  • 1 amsa
  • 1 yana da wannan matsala
  • 1 view
  • Amsa ta ƙarshe daga FredMcD

spadovan
spadovan
more options

We started to get "JSF1064: Unable to find or serve resource,..." log messages when migrating to Firefox 60.x

I looked into the actual TCP requests via Wireshark. The log messages correspond to HTTP requests that are canceled immediately after submitting them, before the server could send the response. I strongly suspect the "Race Cache With Network" feature which was enabled in Firefox 59 (released March 13) to be the cause.

With this feature, Firefox _may_ send requests for cached resources concurrently to the local disk cache and the actual network server. Whichever result arrives first is used - the other request is canceled (which would cause a log message about a "Broken pipe", as with other connection aborts).

The feature can be disabled in Firefox in about:config by setting network.http.rcwn.enabled to false. For me, I stopped getting log messages after setting this to false. Of course this is not a solution.

Please set property network.http.rcwn.enabled to false by default in next versions.....thanks

We started to get "JSF1064: Unable to find or serve resource,..." log messages when migrating to Firefox 60.x I looked into the actual TCP requests via Wireshark. The log messages correspond to HTTP requests that are canceled immediately after submitting them, before the server could send the response. I strongly suspect the "Race Cache With Network" feature which was enabled in Firefox 59 (released March 13) to be the cause. With this feature, Firefox _may_ send requests for cached resources concurrently to the local disk cache and the actual network server. Whichever result arrives first is used - the other request is canceled (which would cause a log message about a "Broken pipe", as with other connection aborts). The feature can be disabled in Firefox in about:config by setting network.http.rcwn.enabled to false. For me, I stopped getting log messages after setting this to false. Of course this is not a solution. Please set property network.http.rcwn.enabled to false by default in next versions.....thanks

All Replies (1)

FredMcD
FredMcD
more options

I called for more help.

Separate Security Issue: Update your Flash Player or remove it using these links; http://helpx.adobe.com/flash-player/kb/uninstall-flash-player-windows.html Uninstall Flash Player | Windows http://helpx.adobe.com/flash-player/kb/uninstall-flash-player-mac-os.html Uninstall Flash Player | Mac

Note: Windows users should download the ActiveX for Internet Explorer. and the plugin for Plugin-based browsers (like Firefox).

Note: Windows 8 and Windows 10 have built-in flash players and Adobe will cause a conflict. Install the plugin only. Not the ActiveX.

Flash Player Version: Version 29.0.0.171

https://get.adobe.com/flashplayer/ Direct link scans current system and browser Note: Other software is offered in the download. <Windows Only>

https://get.adobe.com/flashplayer/otherversions/ Step 1: Select Operating System Step 2: Select A Version (Firefox, Win IE . . . .) Note: Other software is offered in the download. <Windows Only> +++++++++++++++++++ See if there are updates for your graphics drivers https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration