the site was blacklisted after which i brought the site down,fix the problem and asked for a review from Google. Google reviewed and certify that it is no more containing malware and i also used safebrowsing to scan it afterwards, it was passed as a safe site, but Chrome and Firefox still displaying the site as a deceptive site..what to do?
Related
Years ago I did something in Chrome that I can't remember and can't find now to unwind. I have a fake location saved for Chicago somewhere, it was because I had YouTube TV years back overseas and needed it to see Chicago as my location. Now it's creeped back to haunt me, a lot of airline sites and certain other sites don't work in that Chrome profile.
It's not in Sensors, I know where that setting is and it's off, besides that should be for only that page and when the console is open if I understand it correctly. This issue is applying for all pages, but only in Chrome and with that one Google profile. I have other Google profiles that are unaffected.
This has been driving me absolutely mad this past year or so when I've been getting blocked out of more and more sites, being detected as a bot.
Checked sensors, nothing there. Only affects Chrome and only on one profile. I can switch profiles and it works fine. Also nothing in extensions that would affect location.
Google Chrome says it is blocking ads on our web application, but our application does not have any ads in it. This is a SAAS application and includes regular downloading of data files.
The Chrome dev console says: "Chrome is blocking ads on this site because this site tends to show ads that interrupt, distract, mislead, or prevent user control. You should fix the issues as soon as possible and submit your site for another review."
Our application has also been marked by Google as being Deceptive for this reason.
Google's resources for resolving the problem are very unhelpful. All they say is to remove intrusive ads, but not what ads we are displaying in particular.
Any knowledge of this problem and possible solutions? Maybe some bad practices to avoid?
I am having this weird issue with google chrome browser. whenever i try to inspect element and open the developer tools, it automatically reloads the page.
Is there anyone else having the same issue ? How do you solve it ?
I just solved this today! For me, the extension was: Instagram Download Video & Image (but there appear to be about 30 affected plugins). Check the ARS link for all of them...
To quote ARS Technica...
...researchers from Prague-based Avast said they found 28 extensions for the Google Chrome and Microsoft Edge browsers that contained malware. The add-ons billed themselves as a way to download pictures, videos, or other content from sites including Facebook, Instagram, Vimeo, and Spotify. At the time this post went live, some, but not all, of the malicious extensions remained available for download from Google and Microsoft.
The plugins have been removed, you can't download them at the chrome plugin site anymore, and the problem of the page refreshing when you inspect no longer happens.
2021, July Update: It seems like other extensions are slowly being weeded out as security threats by Google. Just the other week, the extension TikTok Video Downloader was similarly removed.
Recently I’ve enabled a Content Security Policy for my web app. Based on my own testing in Safari and Chrome, everything works fine. I’m using report-uri.com to get error reports.
So far, the only reports I received are a number of blocked requests from Chrome browsers to Google Fonts for the Open Sans font. However, we don’t use Google Fonts or Open Sans in this project at all. I’ve searched through the whole source code (including libraries) for related terms, which confirmed that we don’t do anything with Google Fonts or Open Sans.
The reports don’t include useful information to find where the request to Google Fonts was made from, so I don’t know where to look any more. Because the reports only come in at some times during the day, but our app is used by a number of users throughout the whole day, I suspect it’s just one user. Maybe some kind of browser extension is causing this?
Does anyone have an idea how these requests could be caused? I’d like to make sure it’s not something on our end.
It's possible that a poorly made Browser Extension is attempting to load content in an un-kosher way. I haven't experienced it myself but there's at least one article out there on the phenomenon discussing how to avoid it from the perspective of an extension dev. Unfortunately there would be basically no way to be sure without finding the actual user(s) in question and asking them or testing from their machine.
It's also possible that user-side malware taking over the browser could load external elements on your page much like a browser extension; it's rather unlikely they'd bother loading Open Sans and nothing else, though.
As usual be sure to test your site in a variety of configurations and browsers (a favorite of mine is incognito mode in both Chrome and Firefox to ensure my cache/service worker aren't deceiving me). I would say if you don't find anything it's highly likely that it's in fact a user-side issue.
WebGL does not work in the following three scenarios:
(for the 'test webgl' site used get.webgl.org)
1 Start chrome, Google search for the 'test webgl' site, click on the link in the search result.
2 Go to the 'test webgl' site from a link in an email.
3 Start Chrome from a short cut or command prompt, "C:\Program Files\Google\Chrome\Application\chrome.exe" http://get.webgl.org/
This only happens when Chrome is not already running. In other words WebGL does not work when chrome starts up. However it does work if chrome is already running.
The best demonstration is scenario number 3, above. This starts chrome and goes to http://get.webgl.org/ and Webgl does not work. Then do exactly the same again but this time with chrome already open and Webgl works.
Would very much appreciate feedback or a solution, thanks.
Have also created various test sites in html, javascript and webgl, in order to find a work-around. For example if webgl is not available then allow the user to click on a link to open the page in a new tab, this does not work. However if the user opens a new tab then loads the page, webgl is detected and works.
In short, if a customer opens chrome and searches for your website (that has webgl content). Then clicks on the link, webgl will not work. It does not seem reasonable to then instruct the customer to open a new tab and then go to the same website a second time. So far have not been able to find a solution so that it just works without the customer having to fiddle around.
I realize that this may be a chrome issue as it does not occur in firefox, however am trying to find a javascript solution rather than waiting for chrome developers to fix it.
Thanks for any suggestions.
(Windows XP Pro, Chrome V36)
Hi Mack,
Thanks for your reply. The majority of visitors to my web site have XP and Chrome. I should imagine that this is true for quite a lot of peoples, websites.
Problem 1 The first fallback I had on my website was to detect if webgl is supported. If yes then continue as normal. If no then display a help page. This was simple and worked, however, google crawlers do not handle the javascript very well, therefore always index the webgl help page, rather than the home page.
Solution 1 Managed to fix this by having a popup box appear when webgl is not supported, giving the user a choice of whether to continue or go to the help page. The conditional code that processes the user response is arranged so that if the user is a google crawler then it simply 'falls through' and displays the html content of the home page, and not the help page.
There are lots of web sites that seem to have this same problem, including get.webgl.org, in other words, if you do a google search for a website, and that site contains webgl detection and fallback code, the search result always shows the fallback content, rather than the authors intended main content.
Problem 2 Now that I finally have the home page listed correctly by google, found that am still losing many customers, as they are starting chrome, searching google for my site 'suit yourself shirts', clicking the link in the result and being told incorrectly that webgl is not supported.
Am very interested in your solution but do not quite understand how it works. Have tried detection then page refresh or load the page in a new tab or display a link for the user to load the page, but none of these methods seem to work. Seems like quite a fundamental problem that would effect many webgl websites. Would be very greatfull if you could explain your suggestion a little further. Thanks for your help, kind regards - Gary