Issue Summary

When using Firefox to access a workspace that has IP access control enabled, using an IP that is not allowed, a message will be shown informing to the user the access was blocked due to the IP.

After changing the IP to a different one (connecting to an allowed VPN, for example) and refreshing the page, Firefox still uses the old TCP connection with the not allowed IP blocking the connection to the workspace. It only successfully loads after a hard refresh.

Steps to Reproduce

1. Start out NOT connected to VPN
2. Open a new tab in a browser (Firefox or Chrome) and browse to a workspace that has allowlisting using an IP that is not allowed
3. Observe error "You're currently blocked from this page // To access this page, make sure you are on a private network that allows you access, which may require you to connect to a VPN." (expected)
4. Now connect to a VPN that has allowed IP in the workspace
5. Try again to access bitbucket.org. Here the behavior diverges depending on the browser.
   a. In Chrome, access to bitbucket.org works now, either with in-app transitions or with a full page refresh. (expected)
   b. In Firefox, access to bitbucket.org does not work. I still see the IP blocked error page. This happens for both in-app transitions (clicking "Pull Requests" or "Repositories" in the header) and also for a full page refresh (click browser Refresh button or open a new tab). (bug / not expected)

There are two workarounds that each fix the problem:

1. Shift+refresh in the browser, for a "hard refresh" AKA "Reload (Override Cache)" (ref: Mozilla Support)
2. Quit and re-open Firefox

Expected Results

1. Maybe the front-end can detect the network change and force a re-connection.
2. Maybe the IP allow-listing feature can be changed so that any persistent TCP connection is closed after the "To access this page, ..." error is sent.
3. Maybe the "To access this page, ..." can trigger its own hard-refresh
4. Or at least the text could be updated to mention that a hard refresh is needed for Firefox users.

Actual Results

After a normal page refresh, Firefox still uses the old TCP connection with the not-allowed IP. 

Workaround

1. Shift+refresh in the browser, for a "hard refresh" AKA "Reload (Override Cache)" (ref: Mozilla Support)
2. Quit and re-open Firefox