Why Google Location Service not working in Chrome? - javascript

Why Google location services are not working? I already have the code which is working perfectly in browsers other than Chrome. It was working in Chrome till last Wednesday. And not only this, it is indeed not working for any other site who have used this code. Is this due to SSL?
As an example, please visit http://stores.hypethegym.com/hype-sector-4-gurgaon-339/Map
When you open this page, you should get a notification saying "Share your location" in firefox & IE10, but in Chrome, there is a problem.
We are getting following error in Chrome:
"getCurrentPosition() and watchPosition() are deprecated on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS...."
Thanks for the help in advance.

Related

Firefox: WebRequest API vs Deceptive Page

I'm developing a Firefox add-on which does block the malicious URLs. The problem is that sometimes Firefox render its own deceptive warning page and sometime it allows the extension to render its own warning page.
How can I bypass the deceptive page warning programmatically?
The above behaviour is working fine on Chrome.
Abdul Basit.
The easy way is with the privacy WebExtension API, here the documentation on the Mozilla Developer Network (MDN):
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/privacy
Access and modify various privacy-related browser settings. To use the
privacy API, you must have the "privacy" API permission.
You can already use services.safeBrowsingEnabled for Chrome, Opera, Edge, but Firefox not yet.
You can play around with the request status code 400, because it is related to the deceptive request routing.
Good luck.

firebase.auth().signInWithPopup() not works with Chrome extension on Linux/Mac

I am developing a chrome extension.I have used firebase google sign for authentication using firebase.auth().signInWithPopup() method.
It works well with Windows.But it do not works with Linux/Mac OS. A popup window appears for a while then it disappears.
Please suggest Solution.

Error parsing header X-XSS-Protection - Google Chrome

I upgraded Google Chrome to Version 64.0.3282.140 (Official Build) (64-bit) on a Windows 10 machine. Once I did, I am getting this error on my site within the developer tools console. Not real sure where to start. I did see a similar issue last year that was an issue with youtube (also in the url), but I haven't seen any solutions.
Error parsing header X-XSS-Protection: 1; mode=block;
report=https://www.google.com/appserve/security-bugs/log/youtube: insecure
reporting URL for secure page at character position 22. The default
protections will be applied.
16:07:31.905
I'm also seeing the issue when I go directly to youtube via the embedded url so it's not just on my site.
UPDATE
I've attached a photo of the headers in the response that indicate the google.com url that appears to be generating the issue.
It's a known bug in the current Google Chrome and Chromium:
https://bugs.chromium.org/p/chromium/issues/detail?id=807304
In the current version of their browser, the Chrome developers had restricted the X-XSS-Protection's report field URL to the same domain origin for some security reasons. So, when you embed a video with some embed code, as it downloads from another server where the header "report=https://www.google.com/" is set, and while your page is not hosted at the google.com domain - the error message occurs.
Yet, all minor sites (including youtube.com) are sending report URL with different origin domains in it. Probably, they are not even aware of this recent change in Chrome. So either YouTube will change their headers or Chrome developers will revert this. There's nothing that we, as end users, can do. Just wait till they sort this out.
UPDATE:
The issue has been fixed in Version 66.0.3359.117 (Official Build) (64-bit)
The issue has been fixed in Google Chrome new update.
Version 66.0.3359.117 (Official Build) (64-bit)
Make sure you have updated Chrome to this version.

Limit on number of cookies allowed? - err_spdy_protocol_error

On Chrome and Firefox I sometimes get the following error err_spdy_protocol_error
once I call the following website https://checkideas.com/.
I have researched on this topic on the internet and on this platform as well. I also found a working solution. Once I delete all the cookies and reload the webpage the error does not emerge.
So if you click on the website for the 1st time it will definitely work. But once there are number of cookies given the website cannot always be called. This is only the pattern I have identified so far. However I would like to have a sustainable solution.
What do I have to do to avoid this issue so that this issue does not occur? What is the source of the error?
Unfortunately following responses on similar questions did not answer my question:
Console errors. Failed to load resource: net::ERR_INSECURE_RESPONSE
What mean ERR_SPDY_PROTOCOL_ERROR in nginx?
I also cannot identify any issue with the certificate.
This error is related to the SPDY Protocol or an antivirus setting.
Updating to a later version of the browser should help fix the error (Google Chrome and Mozilla have dropped support for the SPDY Protocol.
This article contains methods that should help you fix the ERR_SPDY_PROTOCOL_ERROR
on Google Chrome or Mozilla.

HTML5 Geolocation timing out with a HTTP 400 using Chrome

When attemping to use HTML5 Geolocation method, I consistently get TIMEOUT errors when using Chrome. I know similar questions have been asked, but all answers I've read direct the developer to use HTTPS & not a local env (ie: file:///).
I'm testing with the exact code sample from the Example block at Mozilla Geolocation.getCurrentPosition().
I'm using Chrome Version 54.0.2840.98 (64-bit).
I am using SSL / HTTPS (not self-signed, cert has valid cert auth).
I have confirmed the Location Service is allowed for the domain in question in Chrome Preferences.
I have successfully tested the same code using Safari.
I have tried with & without a valid Google API key with no difference.
I have enabled Google API Billing for the specific project that this API key is tied to in Google Dev Console.
Here's a screen shot of the error in console.
I don't know where else to look or what to try. Any help is greatly appreciated.

Categories

Resources