Open fmarier opened 4 years ago
An alternative to proxying these request would be to remove this page from Brave entirely.
Yes we should just not serve anything from this domain
Let's go ahead and remove chrome://new-tab-page entirely.
Not sure when it was done, but that page is gone now.
Page is still up. I think there was a typo chrome://new-tag-page vs chrome://new-tab-page
There is now a crash that happens when you click the search box on brave://new-tab-page - see https://github.com/brave/brave-browser/issues/36393
I agree that we should consider removing this page. There are folks using it though - we'll want to account for that if we do decide to remove it.
I'll add this to Desktop papercuts
@bsclifton How about redirect brave://new-tab-page to brave://newtab? It would be simplest fix.
@simonhong that works for me... @rebron WDYT?
@bsclifton @simonhong The redirect makes sense to me.
Needs some more thought before we start work. It might be good to change the behavior to proxy instead of removing this page. There are folks using this page actively - a few users have commented they will stop using Brave if this is removed. We could also potentially remove the Google logo and put our branding there too
Description
Open
chrome://new-tab-page
triggers requests to Google servers which don't go through our proxy.They go through a special URL scheme:
Steps to Reproduce
mitmproxy --socks --port 9000
brave-browser-nightly --proxy-server="socks5://localhost:9000"
chrome://new-tab-page
Actual result:
The following requests to Google servers are triggered:
Expected result:
These should be proxied.
Reproduces how often:
Always.
Brave version (brave://version info)