Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hard refresh of Tor tab usually does not get new IP #1512

Closed
LaurenWags opened this issue Oct 11, 2018 · 1 comment
Closed

hard refresh of Tor tab usually does not get new IP #1512

LaurenWags opened this issue Oct 11, 2018 · 1 comment
Labels
closed/duplicate Issue has already been reported closed/invalid

Comments

@LaurenWags
Copy link
Member

Description

Found while testing 'New circuit' from #1270 (comment) Most of the time when doing a hard refresh of Tor tab a new IP is not fetched. However, 'New Tor Identity' works each time.

Steps to Reproduce

  1. Open Tor window.
  2. Navigate to check.torproject.org or whatsmyip.org
  3. Do hard refresh of the page --> IP may or may not change
  4. Repeat step 3 a few times. --> IP does not change
  5. Open a new tab in Tor window. Navigate to same site. --> same IP is displayed.

Actual result:

IP generally does not change. If you use 'New Tor Identity' you will get a new IP each time.

Expected result:

New IP without having to use 'New Tor Identity'.

Reproduces how often:

fairly easily, but sometimes IP does change.

Brave version (chrome://version info)

Brave 0.55.12 Chromium: 70.0.3538.45 (Official Build) beta(64-bit)
Revision cbdc32e4334458954e9def214d7e5fa1ca1960eb-refs/branch-heads/3538@{#830}
OS Mac OS X

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds? yes
  • Does it reproduce on browser-laptop? no, hard refresh on 0.25.0 generates new IP

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields? n/a
  • Is the issue reproducible on the latest version of Chrome? n/a

Additional Information

Reproduced by @srirambv

@LaurenWags LaurenWags added this to the Releasable builds 0.55.x milestone Oct 11, 2018
@bbondy bbondy modified the milestones: Releasable builds 0.55.x, 1.x Backlog Oct 11, 2018
@rebron rebron added the priority/P2 A bad problem. We might uplift this to the next planned release. label Oct 26, 2018
@rebron rebron modified the milestones: 1.x Backlog, 0.57.x - Dev Oct 26, 2018
@rebron rebron removed this from the 0.57.x - Dev milestone Oct 30, 2018
@bbondy bbondy added this to the 1.x Backlog milestone Oct 30, 2018
@darkdh darkdh self-assigned this Oct 30, 2018
@tildelowengrimm tildelowengrimm added priority/P3 The next thing for us to work on. It'll ride the trains. and removed priority/P2 A bad problem. We might uplift this to the next planned release. labels Oct 30, 2018
@tildelowengrimm
Copy link
Contributor

This functionality hasn't been implemented yet: #1137 is the open issue for this work.

@tildelowengrimm tildelowengrimm modified the milestones: 1.x Backlog, Dupe / Invalid / Not actionable Oct 30, 2018
@tildelowengrimm tildelowengrimm added closed/duplicate Issue has already been reported and removed bug priority/P3 The next thing for us to work on. It'll ride the trains. labels Oct 30, 2018
@bbondy bbondy removed this from the Dupe / Invalid / Not actionable milestone May 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed/duplicate Issue has already been reported closed/invalid
Projects
None yet
Development

No branches or pull requests

6 participants