GET errors in console when loading cached content with no network connection

[darrenklein]

Hi - thank you for all of your work.

I'm using rack::offline to cache content for users to access when they don't have an internet connection.

In both development and production, there seems to be an issue with the caching. First, I visit the page, and the cached is updated. When I turn off my network connection in development, the page seems to function ok, but I get the following errors in the console.

GET http://localhost:3000/assets/application.self-e80e8f2318043e8af94dddc2adad5a4f09739a8ebb323b3ab31cd71d45fd9113.css?body=1 net::ERR_CONNECTION_REFUSED
GET http://localhost:3000/assets/jquery.self-660adc51e0224b731d29f575a6f1ec167ba08ad06ed5deca4f1e8654c135bf4c.js?body=1 net::ERR_CONNECTION_REFUSED
GET http://localhost:3000/assets/jquery_ujs.self-e87806d0cf4489aeb1bb7288016024e8de67fd18db693fe026fe3907581e53cd.js?body=1 net::ERR_CONNECTION_REFUSED
GET http://localhost:3000/assets/application.self-377610cd7c1509e934744c810e3b4cf672dfbcacac3274e7d039827e2ae0fcc7.js?body=1 net::ERR_CONNECTION_REFUSED

In production, I am getting a similar set of errors, although it is only for two files...

Can you explain what these files are, and how I can clear these errors?

Again, many thanks.

[darrenklein]

Ah - I have just realized that these files relate to the application pipeline and shouldn't effect my performance, since the scripts and stylesheets for my cached pages are all tucked into the cache manifest. It would still be nice to know if I can avoid them though.