During some usability tests we seemed to get the same IP address more often than expected. Figure out why and whether there is a bug here.
TEST PLAN:
search 'what is my IP' on a tor tab
remember what duckduckgo says the IP is
click on a search result that shows you your IP.
it should show a different IP than what duckduckgo showed
Based on my testing I'm pretty sure there is a bug here.
STR:
re above,
changing 3rd step to open in a new tab and it works.
The circuit seems only been determined when first request shows per tab.
And I fount out doing a Refresh after step 3, it show different ip than DDG.
So it seems like proxy setting is not able to applied in time before the request processed
Examination on the wire between brave and the tor daemon reveals:
I'm working on a fix which will block request until proxy config is reload
Is this a race between the caller of CreateRequestContextForStoragePartition and TorSetProxy or something? Why doesn't the CONFIG_UNSET return from GetLatestProxyConfig already block it?
because they are running on different threads, UI vs IO.
@diracdeltas mind adding a test case for QA?
@kjozwiak yup, the test plan is basically https://github.com/brave/browser-laptop/issues/14390#issuecomment-396682930t - i'll copy it into the issue
Thanks @diracdeltas 馃憤 Wasn't sure if those were sufficient enough so figured I would ask you just incase!
Verified on Windows 10 x64 using
2042c457.1.167.0.3396.87Verified on Ubuntu 18.04 x64 using the following build:
0.23.16 2042c4572e43fed49765fb3fc8f26d5a7293ac75 7.1.167.0.3396.87Verified with macOS 10.12.6 using
Most helpful comment
@kjozwiak yup, the test plan is basically https://github.com/brave/browser-laptop/issues/14390#issuecomment-396682930t - i'll copy it into the issue