Caching Issue when opening a new tab at the same time using a proxy
Reported by
sius...@gmail.com,
Jun 10 2016
|
||
Issue description
Chrome Version : 51
URLs (if applicable) : Any webpage
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: OK
Firefox: OK
IE: OK
What steps will reproduce the problem?
(1) E.g. in MacOS, setup to use a proxy, set to continue where you left off when opening Chrome.
(2) launch Chrome, simply open a new tab. Note what is shown to the new tab.
What is the expected result?
Supposedly, it should show the default Google search page.
What happens instead?
Instead, it shows our proxy default page.
Please provide any additional information below. Attach a screenshot if
possible.
Once you clear the cache, the new tab will be back to normal again, showing the
default search page.
Our theory is that somehow during that open new tab routine, there is some kind of a bug where Chrome doesn’t get the newest proxy/pac information and it uses something it cached, when it fetches info for that “new blank tab” content (while it’s blank, it fetches some recent sites, etc.).
,
Jun 14 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by rnimmagadda@chromium.org
, Jun 14 2016Labels: Te-NeedsFurtherTriage