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.
Related
When i try to open a particular URL in the staging environment am getting 403 Access Forbidden in Chrome (tried IE, Firefox as well ). The same site is opening to the person sitting next to me.
both are connected to same network, tried clearing cookies , tried opening from different browsers .
Anything that i should be looking in particular, in this scenario ?
The application is working on my Local Tomcat server. For some pages Firefox suspends, the status shows "Waiting for gg.google.com". The same page is easily achieved by Chrome.
Also, I need to mention that some icons with URLs on the Web page are not present in my server, so Firefox is losing time trying to get them
Yes, as Olaf Knock hinted, disabling JavaScript debugging in Firebug solved the problem. See https://briancaos.wordpress.com/2009/07/01/waiting-for-gg-google-com/
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.
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).
I have a website written in HTML5 and have already added it to iis7. I checked to make sure that the path was correct, and both the path and the authentication are reported as being correct by iis. I have a personal DNS that I am using to host the site, and I have the website in IIS being hosted by that DNS. Whenever I go to browse to the site, internet explorer kicks back a page saying it could not connect to the page. It will not let me diagnose any connection problems. Any idea what could be going wrong and how I can fix it?