Issue 162705 in chromium: Chrome bad proxies list in about:net-internals#proxy shows incorrect date.

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Area-UI Pri-2 Via-Wizard Type-Bug OS-Linux

New issue 162705 by pia...@google.com: Chrome bad proxies list in
about:net-internals#proxy shows incorrect date.
http://code.google.com/p/chromium/issues/detail?id=162705

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like
Gecko) Chrome/24.0.1312.14 Safari/537.17

Steps to reproduce the problem:
1. Start Chrome ToT with a proxy PAC configured to point to a bad proxy.
2. Load a page.
3. Observe the bogus date in about:net-internals#proxy

What is the expected behavior?
A valid timestamp is shown.

What went wrong?
To repro, start Chrome with:

./out/Debug/chrome \
--ignore-certificate-errors \
--disable-fre \
--clear-cookies \
--clear-cache \
--disable-default-apps \
--no-experiments \
--no-first-run \
--proxy-pac-url=file:///home/piatek/demo-pac

where /home/piatek/demo-pac contains:

function FindProxyForURL(url, host) {
if (url.substring(0, 5) == "http:") {
return "PROXY proxy.invalid:8080; DIRECT";
}
}

This conditional proxy use will allow you to open about:net-interals#proxy
before loading a page. When a page is loaded, a valid timestamp appears.
After refreshing the display, however, a timestamp in 1970 is shown.

Note that this does not appear to break functionality. Pointing to a valid
(albeit temporarily down) proxy will result in a retry after 5 minutes,
despite the bogus timestamp displayed. (Seems like a FE/backend sync issue
-- push path of the bad proxy info works, but not pull.)

Did this work before? Yes 24

Chrome version: 25.0.1336.0 (169452) Channel: dev
OS Version: precise

[chro...@googlecode.com]

Updates:
Labels: Area-Internals Internals-Network-Proxy

Comment #1 on issue 162705 by cben...@chromium.org: Chrome bad proxies

list in about:net-internals#proxy shows incorrect date.
http://code.google.com/p/chromium/issues/detail?id=162705

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Labels: -Pri-2 Pri-3

Comment #2 on issue 162705 by mme...@chromium.org: Chrome bad proxies list

in about:net-internals#proxy shows incorrect date.
http://code.google.com/p/chromium/issues/detail?id=162705

My guess, without looking at the code, is we're getting the proxy info from
the page before it's fully loaded, and we have the time offset. Then once
we have the offset, we don't refresh the page on the next poll, because the
data hasn't changed.

I've been thinking that to fix issues like these, we could load the
initialization data before onload, or in onload - Either embed it as
Javascript, or use a sync "XHR" to get the data when we're initializing
everything. Regardless, not a big issue.

[chro...@googlecode.com]

Updates:
Status: Available
Labels: -OS-Linux -Internals-Network-Proxy Internals-Network-Logging

Comment #3 on issue 162705 by ero...@chromium.org: Chrome bad proxies list

in about:net-internals#proxy shows incorrect date.
http://code.google.com/p/chromium/issues/detail?id=162705

I can reproduce.

The data for expiry is intact, it is just the display on net-internals that
is affected.

It happens if you load with the #proxy tab in foreground (i.e.
chrome://net-internals/#proxy).

If you load a different tab first (like chrome://net-internals) and then
switch to #proxy tab, it is filled correctly.

Like Matt said, what must be going on is the proxy polled data is being
received before the Constants (not sure why that would happen). We
shouldn't dispatch any of poll observers until the Constants have been
received.

[chro...@googlecode.com]

Comment #4 on issue 162705 by mme...@chromium.org: Chrome bad proxies list

in about:net-internals#proxy shows incorrect date.
http://code.google.com/p/chromium/issues/detail?id=162705

It probably happens because it's getting a result from a poll request from
the previous page - reloading a WebUI page reuses the old RenderView, and
doesn't stop in-flight WebUI messages, so the results from the last poll
from the page before reload is probably being handled by the net-internals
page after reload.

[chro...@googlecode.com]

Comment #5 on issue 162705 by ero...@chromium.org: Chrome bad proxies list

in about:net-internals#proxy shows incorrect date.
http://code.google.com/p/chromium/issues/detail?id=162705

It happens with initial loads too, not just reloads (as long as the opening
tab is the #proxy one), so I don't think it is lingering polls.