Chrome is blocking json downloads - is there a way to prevent this? - json

Today, Chrome started blocking downloads of json files for us. We use them in our internal content management system for moving files from one environment to another. But it isn't just us. We also use Firebase and can't do an export from there either. I know about the workaround to click Show all and keep the "dangerous file", but how can we prevent Chrome from blocking them in the first place?

There seems to be an issue with Chrome blocking various extensions downloads, hopefully this gets resolved soon.

Related

Unable to log into Bitbucket on Chrome

When i tries to log in to Bitbucket (web-based version controller) on Chrome (google chrome web browser), i consistently get,
Oops, you've made a malformed request.
If you came here from a link we sent you, please contact support.
This can happen on Chrome. (works fine on Chrome incognito) This issue occurred when i try resetting my password.
then, i founded a solution from Atlassian Cloud Support. this
but, that's not resolve my problem.
In my research, it seems that people have experienced this error before, but none of worked solution i didn't found.
Any help some else is appreciated!
Thanks.
First thing - try to log into BitBucket in another browser, or in incognito mode:
Windows: ctrl + shift + n
Mac: cmd + shift + n
If it doesn't work then your best bet is to contact Atlassian support.
But if it works, then it's a big chance that an extension is causing the issue.
What you should do is disable all your extensions (type in the URL bar: chrome://extensions) and re-enable each extension, one by one, until you find the culprit.
For me it was this extension causing the problem:
Library Detector v5.6.0
I hope this helps you.
As snishalaka mentioned, https://poperblocker.com/ caused my atlassian Oops, you've made a malformed request problem. Disable it then login. Finally, you can turn on again.
As mentioned in the comments, just click 'Allow Popups' in the site in your popup blocker plugin and it will work fine.
Because it works in incognito, it sounds like there's some bad caching or something along those lines. Navigate to Bitbucket, open developer tools (menu -> More Tools -> Developer Tools), navigate to the Application tab, and in the top section of the left pane, click Clear storage. Now in the right pane, you should see several checkboxes and a "Clear site data" button. Click that, reload the page, and try again.
I had the same issue, couldn't login to Atlassian with Chrome. Strangely it was working on incognito. This lead me to checking my Chrome Extensions. One of the extensions I had installed, which was deactivated in incognito, was causing the issue. After removing it, everything went back to normal.
There may be several reasons for this issue. One was, account created earlier and now that was inactive. Other reason can be, login mail used in other bitbucket workspace(in other organization you worked before). So better to send this question to Atlassian support to resolve.
You can raise a question using below form.
ask bitbucket question
search other bitbucket questions
Well the issue for me was due to utorrent extension, soon after i disabled that it started working fine.

Facing issue while trying to run Robot framework script in google chrome browser

I am facing a Chrome popup while trying to run Robot Frame work script:
Microsoft Security Essentials wants to restore your Chrome settings to their
original defaults.
This will reset your homepage, new tab page and
search engine, disable your extensions, and unpin all tabs. It will
also clear other temporary and cached data, such as cookies, content
and site data.
In chrome extension, my developer mode is unchecked, whereas it should be checked.
The Robot Framework automation script is just to open the google Chrome browser and load google search page.
I am using Win 7 Home Basic OS.
I have attached screenshots.
It appears that most Chrome support specialists will ask you to run an anti-malware tool to verify that your system is running normally. These can be found by searching on the popup message.
One Reddit user commented that in his case the problem was resolved by altering the Windows registry:
I finally found a fix for this. There is a setting in the registry
that's causing it.
In the registry it's under
HKEY_CKU\CURRENT_USER\Software\Google\Chrome\TriggeredReset
Delete the TriggeredReset key and then close regedit. Fixed.
This is an API for 3rd party programmers who want to create cleaning
tools. But if the tool isn't written properly, the triggered reset
never gets deleted and we have it always asking.

Chrome extension - using the filesystem API

The filesystem API cannot be used by unpacked extensions, which is awfully great for development.
But then the real surprise came when I realized I can't use it also with my extension packed, because Chrome tells me it cannot find it in the store and is thus greyed out.
Is there any way to actually develop with the filesystem API then?
My goal, in case this is the wrong direction in the first place, is to write some text to a file when some events in the browser happen. The file should be rewritten, rather than creating a new file, which is why I can't use the downloads API.
Is there any way out of this conundrum?
For anyone stumbling on the same issue - a decent solution is to use the chrome.downloads API to download the file in overwrite and incognito mode.
Overwrite will stop the automatic indices added to downloaded file names, and incognito makes the download invisible in the browser except for incognito windows.
The main shortcoming is that it is of course constrained to the user's downloads folder.

Download of Clickonce Application in Chrome marked as Malicious File

It seems that the latest update of Google Chrome 44 to 45 is blocking clickonce applications.
Our clickonce application is working fine and is in production for over weeks.
This morning we got reports that when users tried to download our application it straight end up in the Downloads tab with following message: "[...].application may harm your browsing experience, so Chrome has blocked it. Recover malicious file". After clicking that message a confirmation dialog is shown and if that gets accepted the user can download the application file.
Is anyone else having the same experience with their clickonce applications and do you have any idea how to get around with it?
Thanks for any ideas / help!
(I have sadly not enough reputation to post images, sorry for that)
Elia
It looks like it might have just been raised in the Chromium issue tracker:
https://code.google.com/p/chromium/issues/detail?id=532952
Quoting from there:
My understanding is that if Google has not scanned the file because it is unreachable or isn't aware of it (no public links so it can't be crawled), Chrome will block the application."
In latest version things are worse: There is only Suppress button next to the message "xxx may harm your browsing experience, so Chrome has blocked it" with no links for "recover". The trick is to click on Show all downloads button on far right. There you will see the link for recovering the file that Chrome unnecessarily deemed as malicious.

Open local files(file://) using Chrome

I have an page with some forms. All the links work fine in IE. They open in a new tab nicely when the hyperlink is click by the user; however, I realized that when Chrome is use the link doesn't open. I keep clicking but nothing opens. The only way of opening the file is copying the hyperlink, opening a new tab in Chrome, paste and go.
Form1
Is this something that browser do? Because I tried it with FireFox and doesn't work either?
It there a way of going around? without installing anything in the browser? Because my user loves Chrome.
Thank you in advanced for the responses.
You can't access to files outside your server or "SandBox", sandbox include the files that user push to the browser or to your server.
If the access from browser to a pc files from web pages was possible, it would be a security problem.
The answer is that you can't with your approach and more importantly you shouldn't. Chrome behavior is in fact the right behavior and it protects you from having malicious users and/or scripts accessing your local resources.
The FILE protocol will access local or defined network named resources which will not be available to a remote user that visits the same page. In other words, you may have outsideserver mapped as a network resource/drive but someone else will not (This does not apply to IPs)
Here's what you can do:
Move the code to a server side script(php, asp, etc) and stream the file back out. Found a quick example here on SO. I did not verify it though. Streaming a large file using PHP
Install a webserver on outsideserver and map a new site to the shared folder. You can then reference it via http (http://outsideserver.com/form1.pdf)
Use the below extension for chrome. It will work.
Enable local file links
Below both options are working and tested.
Link 2
Link 3