With latest chrome 104.0.5112.102 build and apache tomcat 8.7.78 version, whenever we are trying to launch webpages after few hours, chrome is not able to read file from disk cache and it is throwing 400 error for js and css files. So webpages are not loading properly. Once we do refresh page(simple refresh or with removing cache) webpage is loading properly.
Related
Using Workbox's Get Started Guide, I have recently gotten a service worker working on my webapp. However, after adding networkFirst, the app did not register any cached js. However, the service worker needed to be restarted and reloaded before any logs showed up in the console.
After adding CSS caching, when I load my webapp in Chrome using localhost, it crashes. The app does not crash Firefox.
I've posted this to bug reports (sw.js file posted there) but thought I'd try here in case anyone has experiences and solved this, or it's an issue with my files or file structure.
mywebsite
--/static
- sw.js
- index.html
- main.js
- manifest.webmanifest
-- /favicons
- manifest.json
I'm using a node.js local server to serve Chrome a three.js page, and Chrome instead of updating the page when I reload it after I've done some changes, it reloads a cached version instead, and will only update it after I clear all history, then close and re-open the dumb Chrome, which is extremely frustrating and inefficient. That doesn't happen with Firefox. Any ideas?
node.js server run on a .bat file inside the working folder:
http-server -p 8000
exit
on address bar:
http://localhost:8000/mypage.html
I want to inspect and debug a Chrome Mobile application on my "chrome pc/machine",
so I've followed [this](http:// eveloper.chrome.com/devtools/docs/remote-debugging-legacy
) Google tutorial.
When I acessed localhost:9222, it lists the correct sites opened on my android chrome.
But the following error occurs when I click on "Inspectable pages". The console show the message
Document was loaded from Application Cache with manifest https://chrome-devtools-frontend.appspot.com/serve_rev/#178678/178678.manifest
Application Cache Checking event
[blocked] The page at 'https://chrome-devtools-frontend.appspot.com/serve_rev/#178678/devtools.html?ws=localhost:9222/devtools/page/0' was loaded over HTTPS, but ran insecure content from 'ws://<localhost>:9222/devtools/page/0': this content should also be loaded over HTTPS.
Uncaught SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
I encountered this problem too.
According to this report Chromium Issue 398817, you can add the --allow-running-insecure-content when launching Chrome.
This worked for me on Windows 7.
I have cache static resources of my website using manifest file
But when I run website when internet is not connected images not shown.
Images also should cache because I putted them in manifest file.
For example I have cached this file but this file is not loaded when the Internet is disconnected.
Here is google chrome console snapshot :
I also had the same problem. I included below in the cache.manifest file & it fixed for me.
NETWORK:
*
Its strange ..
The problem resolved just when I changed images folder name !
I'm trying to make a appcache file but got some problems... I've added the appcache file to the server, here is its content:
CACHE MANIFEST
CACHE:
scripts/jquery-1.5.1.min.js
But after refreshing the page I got all my web site files missing (styles, js scripts, images etc.), I mean they are not loading anymore and browser always try to get them from local cache. But what I want is just to cache some of them, I don't want to specify ALL my files in the appcache (to CACHE section or to NETWORK section), is this possible?
Don't use the HTML5 app cache for what you are trying to do.
Browsers already cache certain resources from a website and you can choose how the browsers should cache the files by manipulating the HTTP headers. For example, Stack Overflow loads their jQuery library from Google and Google sets the HTTP header: "Expires: Sat, 16 Mar 2013 05:41:47 GMT". Every website that links to this file won't have to download it anymore because the browser will keep it in it's cache for the next year.
For the files on your own website you will have to find out which webserver is running your site. For the Apache webserver follow these instructions, for IIS follow these instructions.