I was working on a html5 file which uses geolocation. It was working fine in Chrome version 38.0.2125.111m from both loading the file locally and from a host server. Now, Chrome does not work for geolocation from either resource. I understand the security issue when running the file locally, but it still happens from any website that is running geolocation. I get the error message of "geocode service failed". BUT runs fine from both resources using Firefox. I have a windows 7 x64 laptop. The code that I am using is right off of Google geolocation example...
I've also went to the chrome's privacy-security-location settings and checked to use allow all sites to check location and still the problem continues... Help!
I think I found a clue. I copied the geolocaton file to another website and ran fine using the same chrome version which makes me believe that it is the google api keys that was causing the problem. I deleted the keys for both local and web host and will see in a few days if indeed this was the case. If it is, then I suggest not to establish api keys during development until app is ready for production.
Related
I'm developing an enterprise web app with Vue.js, and I would like to use the Web Serial API in Chrome. On the linux machine that I'm developing on, I went to this Chrome flag chrome://flags/#enable-experimental-web-platform-features and enabled it. Then I did console.log('serial' in navigator) and it returned true, meaning that the flag is enabled. All is good so far.
So I went and did the same thing on the corporate computer I need to be using (running windows 10). I enabled the flag in Chrome, restarted it, and ran console.log('serial' in navigator) on the tab running the web app, but it returns false, which is bad because I need it to be true. But when I run that code on a different tab, it returns true. How could my web app be changing the navigator? So I can't use the Web Serial API on the one computer that needs to be using it and I don't know why.
Any help is appreciated.
UPDATED. The problem is not specific from vue js, you should make the script execute from a secure environment, either localhost or from a ssl secured domain. This security concerns are covered on this draft https://wicg.github.io/serial/#security.
While trying to access my application in google chrome some urls are working fine and some are getting 404 error. My application is working fine in other browsers like IE , firefox ...etc. Please suggest me some information to allow my application working fine for all urls
You have to explore chrome settings for privacy and security, proxy settings etc.
chrome://settings/system. make your proxy settings as system settings instead of manual.
I am receiving the following error when trying to load a PNG (over https) into an iframe on Amazon's mechanical turk:
SEC7117: Network request to https://toucan.cs.colostate.edu/pp/images/125.png did not succeed. This Internet Explorer instance does not have the following capabilities: privateNetworkClientServer
You can view the page here https://workersandbox.mturk.com/mturk/preview?groupId=36TBNKR908TLAX7SKNTTRWW7TFYEDT It works fine in all other browsers.
I can't for the life of me figure out why Edge would be blocking PNG files (JS I can understand) and how to remedy it. Any ideas would be greatly appreciated.
More Info
Windows 10 64bit
Edge 20.10240.16384.0
Have tested on several machines and been able to replicate the problem
Have admin rights on all machines and they are not part of a domain.
Update
It seems to be an issue with the web server that is hosting the image which is running Apache. I placed the image on another apache server and everything worked fine. so then I tried to send the CORS header for all images as explained on https://github.com/h5bp/server-configs-apache/blob/fc379c45f52a09dd41279dbf4e60ae281110a5b0/src/.htaccess#L36-L53
but that still didn't solve the problem. For some reason Edge blocks the request.
The issue is Edge detecting the file server to be part of the local intranet, which is being referred to from a public website.
Related: SEC7117 Error when trying to load a javascript file in MS Edge
The solution is to host the files on a different subnet from what the computer you're accessing it from.
I have been having an issue lately with Google Chrome. Some sites, seems to be completely random, are returning a 503 Service Unavailable error message. The last one I received was from my hosting provider when trying to access my CPanel. I can access the same URL completely fine in Firefox or IE. It seems to be isolated to Chrome.
I have tried the following:
Disabled all extensions
Logged in/out of my Google account
Cleared all cache and history
So far, nothing seems to correct the issue. It's becoming more and more aggravating from what was once a pretty reliable browser.
I am running:
Windows 7
Chrome Version 36.0.1985.143 m
I was hitting the same issue. Mostly, it would occur on intranet sites at work, but it happened with a few exterior sites. Loading in IE Tab would work fine.
I was able to solve the issue by upgrading to 64-bit Chrome. I'm not sure why that fixed it, but I think it had something to do with a conflict between Java and Chrome (It looks like I have both 64bit and 32bit Java installed side-by-side).
My solution:
Uninstall Chrome with clear personal data option selected
Install Chrome again but without admin right (install for your personal
user)
Use Chrome as normal
I have created one HTML5 web app which works in offline mode.I load it first time form server and then when server is off it works perfectly.Webapp url is http://localhost/index.html
Now , if I try to load that webapp first time on any new machine then how can it resolve the localhost url.I have all the resources bundled with webapp.
In this case server is off and browser is not able to locate url http://localhost/index.html
Any idea if webapp can work in offline mode , even if its not connected to server ever.
What you are doing and expecting seems to make sense. It would be smart to check the console in the Chrome Developer tools. Something along the lines of the following should be shown:
You might be serving the manifest file with the wrong content type (should be text/cache-manifest) or the fact that you're working on localhost might somehow interfere (dunno).