I have made this application using Leaflet.js with these plugins: MarkerCluster, Leaflet Map Fullscreen, it's hosted in a Linux server, HTTP apache2.
For some reason, I can't get my current location on the following browsers:
Mozilla Firefox (latest version)
Google Chrome (latest version)
Microsoft Edge
In IE, it gives me the popup to give permission to locate myself, and it works... only once. If I try to locate myself again it behaves like the other browsers above.
And, if I open the link in Instagram dm's it works just fine...
It works also in localhost or if I use location guard browser extension to make my location a fixed point.
What's causing this issue? Is it because it isn't https?
You will have to switch to https if you want to support geolocation on most if not all modern browsers.
For Chrome
Starting with Chrome 50, Chrome no longer supports obtaining the
user's location using the HTML5 Geolocation API from pages delivered
by non-secure connections. This means that the page that's making the
Geolocation API call must be served from a secure context such as
HTTPS.
For Firefox
This feature is available only in secure contexts (HTTPS) [...]
And according to the nice support grid on MDN, Opera and Safari should also require https to enable geolocation.
Related
In recent versions of Chromium (98+), my Yubikey is broken / no longer working to authenticate / register with websites using the FIDO2 U2F standard.
For example this demo site: https://u2f.cloudentify.com/u2fdemo/
Simply nothing happens and this is written to the console:
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('chrome-extension://kmendfapggjehodndflmmgagdbamhnfd') does not match the recipient window's origin ('null').
How can I get this working again?
It turns out that the way U2F was implemented in Chromium was a bit of a hack and has been deprecated since Chrome 95. Here is the Yubikey page. It should have been a smooth transition to WebAuthn, but this is not true for all websites.
How to re-enable U2F API:
Go to this url: chrome://flags/#u2f-security-key-api
Locate "Enable the U2F Security Key API"
Change the dropdown from "Default" to "Enabled".
Restart the browser.
i am working a social network platform and wanted to integrate the live streaming services and also the chat voice and audio calling services. they are all active, except that I keep getting "Sorry your browser does not have webrtc" even after installing this extension on all my browsers, it still says the same for Chrome, Firefox, and Microsoft Edge. The only browser working perfectly well is the apple safari browser. Now I don't know how to fix this.
WebRTC has to work under https environment. That's why your website isn't working. Deploy the application with SSL security.
I created a Vaadin (8.2.0) web app in Netbeans and uploaded it on a Glassfish (4.1) server. I can access the app's home page in Edge and Firefox, however in Chrome I get this message:
Cookies disabled
This application requires cookies to function. Please
enable cookies in your browser and click here or press ESC to try
again.
I double checked my chrome settings and know that cookies are allowed. I even added the server specifically in the allowed list.
What do think is missing?
As Artur Signell mentioned in the comments, the solution was to simply clear all the cached cookies in the Chrome web browser. After that, the app just worked fine and I didn't get that error.
I was having the same problem. I noticed that switching to HTTPS lead to these errors not occurring. The same site would throw this error when I accessed it via HTTP, but if I went to the site via HTTPS, then the problem did not occur.
I have a Google Gadget with Content type=URL that suddenly stopped working. It was running in a Google Site (as the Gadget container). I can access the URL easily outside the scope of the gadget container. Did Google Sites Gadget Container change support for content type URL gadgets?
In the latest version of browsers
Internet Explorer - 11
Firefox - 25
Google Chrome - 31
non-secure contents are not allowed. Please check your gadget URL and also for any other locations in the gadget where URLs are specified with HTTP. Changing those to HTTPS or to protocol independent would fix your issue.
I have two WCF WebHttpBinding-bound self-hosted services. One is set to WebHttpSecurityMode.TransportCredentialOnly and HttpClientCredentialType.Windows. The other is set to None and None.
This service is serving the exactly the intended authentication prompt behavior on Chrome and IE, with correct content types and content. Testing on localhost and remotely (not on a domain). In IE, the default settings for integrated authentication send my credentials immediately to the authenticated service. In Chrome, the default settings prompt me for my windows authentication credentials.
But in Firefox I get no such prompt - just an error in Firebug of 401 Unauthorized and a blank page otherwise. I assume iOS has the same 401 Unauthorized problem, although the debugger console doesn't show any errors - I just get a blank page.
I don't know how relevant the WCF WebHttpBinding is versus a standard IIS-hosted website, but all the other googles I find are about someone trying to STOP the Windows Auth prompt in favor of Integrated Security mode in non-IE browsers. I kind of have the opposite problem - it's not showing up for me.
Is there something nuanced about the webservice response that Firefox and Safari are sensitive to that Chrome and IE are not sensitive to?
I'm testing on Windows 8 with IE 10 and the latest releases of the other browsers at the time of writing.
Thanks!
If I set it to HttpClientCredentialType.NTLM then all browsers work. But as I understand it, NTLM disallows the more secure Kerberos domain credentials (if they're available). I don't want to force a less-secure option!
Kerberos works well with IE and since Chrome shares stuff with IE, it works for Chrome too. For Firefox, you have to enable it. See here. Safari on Mac OS should work but not sure about other OS'.