Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

apply brave UA whitelist to first-party subresources #10904

Merged
merged 2 commits into from
Sep 15, 2017
Merged

apply brave UA whitelist to first-party subresources #10904

merged 2 commits into from
Sep 15, 2017

Commits on Sep 11, 2017

  1. apply brave UA whitelist to first-party subresources 

    fix #10800

Test Plan:
load adobe.com within Brave
open the developer tools via "option + command + I"
select the "Network" tab and reload adobe.com via "command + r"
select on the first resource and you'll notice the correct Brave Chrome/60.0.3112.101 UA
select another resource that's underneath the first one and is from Host:www.adobe.com
the Brave UA should be there
    @diracdeltas
    diracdeltas committed Sep 11, 2017
    Configuration menu
    Copy the full SHA
    e166b26 View commit details
    Browse the repository at this point in the history

Commits on Sep 14, 2017

  1. Added unit test which ensures: 

    - filtering.getMainFrameUrl is called (which also queries webcontents; no test for that yet)
- hack considers subdomain

Auditors: @diracdeltas

.
Auditors:

Test Plan:
    @bsclifton
    bsclifton committed Sep 14, 2017
    1 Configuration menu
    Copy the full SHA
    25c9492 View commit details
    Browse the repository at this point in the history