We are seeing an issue with our pre-production and production native homegrown web app where after 15-30 seconds it appears that the session times out when making the preflight API call in the Chrome browser. Edge v101.0.1210.53 appears to be working. We don't see any other errors in the Chrome inspect console.
We saw this behavior on May 25, 2022 right around when chrome 102 got pushed to the browsers. IF we use inspect and turn off the cache then we still see issues with loading the app.
Testing using chrome 101.0.4951.61 against the same web app on my virtual machine does not reproduce the issue. After the browser updated on the virtual machine, the error was reproduced.
Are there any new features in 102 we could turn off to see if a specific new security check might be at play?
Appears to be a bug in chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=1329248
Work around is to disable this: chrome://flags/#private-network-access-send-preflights
Related
My copy of Google Chrome, on my laptop, fails to register all service workers. If I load any website that has offline functionality, devtools console outputs:
Uncaught (in promise) TypeError: Failed to register a ServiceWorker for scope ('https://googlechrome.github.io/samples/service-worker/basic/') with script ('https://googlechrome.github.io/samples/service-worker/basic/service-worker.js'): An unknown error occurred when fetching the script.
Note that the above error is from https://googlechrome.github.io/samples/service-worker/basic/, which is a technology demonstration made by google, specifically about service workers, specifically for chrome, not something I created. One other interesting thing is that service workers fetched from localhost can be registered with no problem. This would suggest an SSL issue (I think), but then again the host of the above website is github pages (is there any way my browser could be not trusting github pages? I haven't found any evidence to support that).
I get the same error if I directly type navigator.serviceWorker.register("https://googlechrome.github.io/samples/service-worker/basic/service-worker.js"); into the console on the same site.
It's not just a console message: if I load the website, then disconnect from the internet, then refresh the page, the browser reports "no internet" and does not load the website. The same thing happens if I use devtools>Application>Service Workers offline mode. This indicates that the service worker is failing to register. However, the Service Workers devtools tab does show service workers present – it just lists them as "redundant" instead of "active and running". Bizarrely, the "time received" is 1970-01-01.
I'm using Google Chrome Version 89.0.4389.114 (Official Build) (x86_64) on MacOS Big Sur. On other browsers (Safari, Firefox, and any browser on any other computer/mobile device), this error does not occur. I have restarted my Chrome multiple times since I first noticed the error, and updated it once since then. Neither fixed it.
I'm aware of a couple similar SO questions (here and here for example), but all of them have accepted answers about how the website creators can fix bugs in their site. This bug is appearing on websites I did not create, and seems specific to my browser (which I haven't tampered with in any way). The main reason this is driving me nuts is that I really really like Chrome's devtools, and I would like to use them for a current PWA project.
If anyone familiar with Chrome's inner workings knows what could be causing this, or if anyone has solved this in the past, I will be forever in your debt.
So I have been following the following step for past few months:
Log in to Google Cloud Console from Chrome's incognito mode
Activate Cloud Shell
From there, I usually opened Editor and managed my files in a new window
Today while I was following the above steps, this issue raised up:
Basically, I cannot open editor anymore. I have already went through similar posts, and my issue is that I am using incognito where browser extensions or cookies shouldn't be an issue.
I am facing this problem for the first time and if anyone knows what is the cause or any suggestions would be appreciated.
EDIT:
For now Microsoft Edge InPrivate Mode is working for me. I am still interested in fixing the issue for Chrome.
Have reported the issue in Issue Tracker. Please "start" for more attention.
This started happening recently because third-party cookies stopped being supported in Incognito mode as of Chrome 83. Third-party cookies are required for the editor to work because of the way the open-source Theia IDE is integrated into Cloud Shell. The team is exploring various fixes, but in the mean time the following workaround should work:
In Incognito Mode, click on the crossed out 'eye' icon on the address bar.
Click on 'Site not working?'
Click on 'Allow cookies'
Safari problem stems from the same issue, but I am not certain if a similar workaround exists.
I've encountered the same issue myself (I tried this on Chrome running on both ChromeOS and MacOS) - it looks like a bug so in this case I'd recommend reporting it on Google's Issuetracker (you can even put a link to this post).
UNfortunately it looks like it's not just the Chrome browser. I tried this on Safari 13.1 and found the issue you described is also present.
I didn't check other browsers but IssueTracker is the way to go. And be patient :)
We have a web application that runs within a VPN. It has a self signed cert on it and is accessed through the server's IP address.
Part of the functionality of this app are some legacy Java apps (that no longer run in Chrome). Our initial work around for our Chrome users was to run Shell In A Box within an iframe of the web app to run those. All was good until the latest version of Chrome, v45.
What we’re seeing is that appears to be blocking the iframed content (maybe because of the self-signed cert?). If we grab the ShellinABox URL and drop it in a new tab, it works as it used to in the iframe. If we go back to the iframe, it now works. If we close Chrome and open it back up, it still works.
I should also note that we tried the canary builds as well. It's up to v47.x and we still see the same behavior there. We were reading through some of the Chrome group/bug lists and saw some reports that were similar but the "fixes" supposedly going through canary still didn't resolve it.
So, it appears that an exception is being logged somewhere. Does anyone have an explanation for this behavior and is there a way to set this exception without jumping through those hoops?
It turned out it was due to a permissions issue with ShellInABox that didn't reveal itself until v45 of Chrome, for some odd reason.
I have a web app developed with application cache. I am testing it on Windows Phone 8.1 running IE 11 mobile. When the internet connection is turned off the web app loads as expected. My problem is that if I hit the refresh button on the browser when the web app is in offline mode the browser tries to check for an updated manifest file. Since there is no connection it cannot find it and then the cache is rendered in an obsolete state and the browser invalidates the cache. The browser refreshes the web app and then tries to pull the page from the network which fails since I am offline. To summarize, what can I do to prevent the browser from invalidating the application cache on refresh when running in offline mode?
That sounds like a bug to me. Per spec, the applicationCache should only be invalidated (become obsolete) if the request to the *.appcache file returns a 404 or a 410 status. If you are offline, it should instead fail with a status of 0.
I'd suggest to test it with other browsers devices and eventually report it as bug to the IE11 team
Not an answer but my reputation isn't high enough to comment, sorry.
Other people have noticed this too (Why offline web application doesn't work?), so as mentioned already here, it looks like a bug.
Are you testing in the 8.1 release that is available from the Developer Preview app? Or a phone running an official release of 8.1?
I ran into the same problem. I haven't got a solution yet. But i want to list what did NOT work!
Adding IIS Mime Types, as discussed here
Changing .manifest to .appcache, as discussed here
Adding the meta header "cache-control: public" as described here
Also did not work to add the header manually in the webbrowser control of the wp 8.1 cordova web app (in the navigate method).
Deleting the Browser History and local storage in windows phone setting is making the problem even worser
Strangely using developer options in IE and change under the tab emulation to windows phone, the appcache loads succesfull
I hope this list will help other people not to find other solutions.
I am building an intreactive information kiosk for public use. Making it a web app in Chrome. It need to work offline. My solution is using the browsers application cache. Problem: Chrome looses all content in the application cache at crash/power failure. Is this normal behaviour?! Is there a way to hold the content in the event of system failure?
Edit 2012-12-19:
The content of the appcache is not lost, it is still there. But Chrome lost the reference to the data. If I start Chrome with the "--restore-last-session" flag it has the connection to the cached data. This is not a "pretty" solution though...
Clarification: The real problem is when Windows and Chrome starts after a power failure and the network connection is absent. Chrome acts as if there is nothing in the appcache and you get the "No network connection" error. I can't se why it works this way?