Joe13_c00l Posted September 23, 2021 ID:1481162 Share Posted September 23, 2021 Hi, I'm a new member here, and a big fan of MWB (I have Browser Guard installed on all my browsers).  The reason why I'm creating this thread is to report a recent incident with MWB BG. So yesterday, I went to my profile at Microsoft Community (I'm a fellow contributor! 😃) and I decided to make a new thread there. I clicked Ask a question, and before the login page could load, it stopped me and BG appeared saying that it detected malware in one part of the site. Here's a screenshot of the error:   I knew that it's a safe site, so I clicked Continue to site which just threw me into the trash saying that there's a 404 (not found) error. Finally I decided to disable BG and when I refreshed the page, it said that the site has been blocked by an extension. After I managed to sign in, I enabled back the extension and there was no blocking anymore.  System: Windows 10 Pro v21H1 build 19043.1237 Browser: MS Edge (stable), v93.0.961.52 BG version: 2.3.9  Thanks,  Joe13 B-) 2.0 Link to post
Solution gonzo Posted September 23, 2021 Solution ID:1481215 Share Posted September 23, 2021 There had been a block on that specific URI, which was lifted (yesterday) after user complaints and subsequent investigation on our part. Browser Guard is very fond of using cache when possible, as you found out the hard way. Once you disabled/enabled Browser Guard, cache was no longer being used. This happens too often, and I have written a request for modifications to how we employ cache just because of this issue. It is in the works. Sorry for the inconvenience. 1 1 Link to post
Joe13_c00l Posted September 24, 2021 Author ID:1481320 Share Posted September 24, 2021 11 hours ago, gonzo said: There had been a block on that specific URI, which was lifted (yesterday) after user complaints and subsequent investigation on our part. Browser Guard is very fond of using cache when possible, as you found out the hard way. Once you disabled/enabled Browser Guard, cache was no longer being used. This happens too often, and I have written a request for modifications to how we employ cache just because of this issue. It is in the works. Sorry for the inconvenience. OK, thanks for the info and for writing the request! Link to post
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now