Network Requests
This page tests different blocking policies in Brave.
First-Party Sub Requests
By default, Brave does not block first-party subrequests, even if there is a block rule for them.
Trackers & ads blocked (standard): There should be a helpful image in the next column. No resources should be blocked in shields.
Trackers & ads blocked (aggressive):
There should not be an image in the next column. A
request for /static/images/test.jpg?335962573013224749
should be blocked because of
this filter rule.
Third-Party Sub Requests
By default, Brave blocks whatever third-party subrequests the lists tell us to.
Trackers & ads blocked (standard) and
Trackers & ads blocked (aggressive):
There should not be an image in the next column. A request
for /static/images/test.jpg?335962573013224749
should be blocked because of
this filter rule.
Relative URLs
The below test checks if the blocking engine correctly handles images that should be blocked when requested from relative URLs.
- Default: All third-party cells should be blocked.
- Aggressive: All cells should be blocked.
| Frames | Workers | ||||
|---|---|---|---|---|---|
| Partiness | This | Local | Remote | Service | Web |
Full URL (e.g., https://example.com/image) |
|||||
| First | |
|
|
|
|
| Third | |
|
|
|
|
Same protocol (e.g., //example.com/image) |
|||||
| First | |
|
|
|
|
| Third | |
|
|
|
|
Same host (e.g., /image) |
|||||
| First | |
|
|
|
|