I came across this issue the other day, I have been using the Google Visualization API specifically for a chart.
Everything was working in Chrome and IE but when trying to view the page in Firefox the chart would not display.
I did receive an error in the Firefox developer tools:
ReferenceError: google is not defined
This is from code that looked like this,
google.load("visualization", "1", { packages: ["corechart"] });
google.setOnLoadCallback(drawChart);
As I mentioned above, this was working on other browsers(IE, Chrome) just not Firefox.
Why is the chart not showing in Firefox only? Why is google no longer defined in Firefox?
For this scenario, the issue was caused by un-trusted SSL certificates in my Firefox browser.
As many of us know Firefox does not use the same certificate store as the other browsers that I mentioned.
For this instance the Google certificate was not being trusted. Once the certificate was added as an exception the grid and page functioned as expected.
(For a little more information, the certificate from Google was not being trusted because of network security software)
Related
We have the Google Picker working, but have noticed that the picker code seems to be trying to log events to Google, and is getting 400 errors when doing so.
Looks like Google library code trying to talk to Google infrastructure:
Just a problem with the Google infrastructure, or is there any way to stop this?
Found the problem - it was that third party cookies were disabled (in Incognito mode).
I'm working on W10 box.
One day all Chromium based web browsers (Chrom, Opera) stopped working with any Google based services showing "Cert is revoked" message on SSL access.
Given Cert is:
https://censys.io/certificates?q=37839b99a1c97d649b3d931ff055eba5f1493434
What is very strange Edge browser is working well.
What's more all browers show the same Certificate (checked details) for a given web page but only Edge is working with it.
What's the problem ?
So it's finally solved.
Somehow, have no idea why, my CERT store had 2 copies of the main signing cert called "Google Trust Services -GlobalSign Root CA-R2".
The one used for signing Google services.
Once I delete the "bad" one all browsers work well!
I have a .NET C# program rendering on IIS web server. After adding SSL certificate to the server the program takes up to 5 minutes to respond to my request, only in Google Chrome. If I use the old HTTP URL everything is normal and the page is loaded after 33 sec. Does anyone have a suggestion on what causes this slow rendering of HTTPS web-page in Google Chrome?
According to your description, I suggest you could firstly clear all the chrome's cache and update the chrome to the newest version. About how to troubleshoot google chrome's performance issue, you could refer to this article.
If this doesn't solve your issue, I suggest you could try to use chrome F12 develop tool to check what has happened when you send the request to the server. More details about how to use it, you could refer to this article.
I am using firebase for web push notification it is working perfect when I used it in same domain, but I have only one ssl domain and many non ssl website. So I have plan to use it in iframe and integrate this facility in all my non ssl websites too.
URL is
https://htmlcodeplay.com/notification/notification/index.html?websiteid=3
I have integrate it through iframe like below
<iframe src='https://htmlcodeplay.com/notification/notification/index.html?websiteid=3'></iframe>
I have integrate this lines into my blogger https://allinworld99.blogspot.in. But it is working perfectly in Firefox browser but not in chrome browser. No errors also displayed.
As per this link Does my web application require SSL for Firebase Cloud Messaging for Web to work?. It should not work, but how it is working in firefox browser.
I am not able to find a reference right now, but you want to do
embed a "push notification webpage" inside another via iframe
is blocked by Chrome for security reasons.
I added Google OAuth2 to my website. I noticed that when the website was opened in a embedded browser (web view), redirecting to google auth page (see the link below) will fail with error:
"403 disallowed_useragent".
Here is the link:
https://accounts.google.com/o/oauth2/v2/auth?client_id=813505898895-9vocl0haapnp562pn1hmut2sibregabn.apps.googleusercontent.com&response_type=code&scope=openid%20profile%20email&redirect_uri=http%3A%2F%2Fwww.antgora.com%2Fauth1%2Fsign-in%2Fgoogle&state=6515338772758876.%2F
I get that Google no longer allows OAuthrequests to Google in web view. But here is the strange thing. The google sign in demo
developers.google.com/identity/sign-in/web/sign-in work fine when opened in web view. I managed to find the client_idand redirect_uri used in the demo and replace them into the my google auth link (see the updated link below), the updated link can now magically open in web view.
https://accounts.google.com/o/oauth2/v2/auth?client_id=831371170934-udapit5jhjj56pft5l2drc9gjhfeclf3.apps.googleusercontent.com&response_type=code&scope=openid%20profile%20email&redirect_uri=storagerelay%3A%2F%2Fhttps%2Fgoogle-developers.appspot.com%3Fid%3Dauth58372&state=6515338772758876.%2F
Notice that I changed only client_idand redirect_url and nothing else. Later I found more client_idsthat also works with webview. I am wondering is there any specific settings for these client_ids to work?
Also I want to know what's the recommended fix to:
"403 disallowed_useragent"?
My website has no native app. And most likely, people will just open the website they received on online chat in a webview. I'd like to avoid showing the :
"403 disallowed_useragent"
error when they click *sign-in by Google*.