Brave is blocking parts of our web application due to the file names used

Description of the issue:
Brave ( Version 1.8.95 Chromium: 81.0.4044.138 (Official Build) (64-bit)) is blocking parts of our web application due to the naming of some files

Steps to Reproduce (add as many as necessary): 1. 2. 3.
Create an AngularJS web application that contains beacon or push-notifications in the route

Actual Result (gifs and screenshots are welcome!):

Expected result:
Brave doesn’t block any of our non-tracking web application

Reproduces how often:
Every time

Operating System and Brave Version(See the About Brave page in the main menu):
All. This is web browser related and not OS

Additional Information:
If I access my web application, when it’s running locally and without any file minification, then multiple files are blocked by Brave:

  • localhost:9000/scripts/controllers/push-notifications.js
  • localhost:9000/scripts/services/push-notification.js
  • localhost:9000/scripts/services/beacon.js
  • localhost:9000/scripts/controllers/beacon.js
  • localhost:9000/views/push-notifications.html

When we build our web application for production, minification happens on all JS code and they are combined into a single JS file but the HTML views remain unchanged in their filenames. Accessing that minified version of the web application then only has that non altered HTML file blocked:

So this clearly seems to be an issue with Brave automatically blocking any files with the word “push” or “notification” and/or “beacon” in the file name


I’m the filter engineer for Brave, there is probably no easy fix on Brave side for sites developing notifications/beacons/tracking etc. I would recommend just disabling shields on the site (localhost).

We block those elements due to privacy and annoyance, all 3 are related to push notifications and tracking (beacon.js).

This seems a little silly

We cannot ask our potential and actual users to modify their browser settings to access our site

It also seems a strange method from Brave for blocking. If I were adding tracking to my site and I noticed you were blocking files of a certain name (beacon etc) I would just rename my beacon files to avoid your blocking, which is what I am preparing to do at the moment, in our non tracking site which you have misidentified

Potential and actual users? they won’t have access to localhost. And if its a web notification or a tracker, it should be blocked. “beacon.js” is a commonly used tracker script.

Using localhost was an example to prove that these files are definitely being blocked by Brave

When I run my web application locally, none of the files are renamed. When the web application is deployed to then the files are renamed (due to minification) but our view templates aren’t renamed, so Brave still blocks push-notifications.html

These aren’t web browser push notifications. Push notifications is a section of our web application that allows users to create a mobile phone push notification to their Android/iOS apps

How is blocking that effective long term? It’s not my place to judge your methods really but if I were trying to sneak past your defense, I would just rename my beacon.js file to nothingToSeeHere.js …

I’m just annoyed that I need to break my innocent web applications naming rules to support Brave users

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.