Chrome Network Web Developer Tool tab says Dojo AJAX requests are taking around 44 years to complete

This issue is not related to web framework or server. Issue affects Chrome browser version 31.0.1650.57.

Now issue is fixed and will be delivered with next stable channel update. Fix diff

If you need fix urgently, you can update to dev channel version. Instructions

See this issue for more details.

Very odd. Able to recreate on Chrome 31.0.1650.57 on OSX Mavericks as well. Tested w/ ikea link, noticed Chrome reported 16028.7 days, 41ms latency for resource /us/en/iows/tealium.

Charles proxy shows these headers:

HTTP/1.1 304 Not ModifiedContent-Type: application/jsonLast-Modified: Mon, 18 Nov 2013 18:34:51 GMTCache-Control: public, max-age=7200Date: Sat, 23 Nov 2013 00:32:26 GMTConnection: keep-aliveVary: Accept-Encoding

The proxy app (Charles) reports no such odd time - it shows 40ms.

The lavieenrose.com link caused Chrome to report time of 16028.7 days as well... that seems to be in common.Charles shows:

HTTP/1.1 200 OKDate: Sat, 23 Nov 2013 00:46:37 GMTServer: IBM_HTTP_ServerLast-Modified: Tue, 19 Jun 2012 13:05:34 GMTETag: "5c487f-1a15-4c2d2f01a0380"Accept-Ranges: bytesVary: Accept-EncodingContent-Encoding: gzipContent-Length: 1738Content-Type: application/x-javascript

My conclusion is this isn't a server response or headers issue. I think this is a Chromium or WebKit dev tools issue.

Here's HEAD of the dev tools JS object that represents the http request which rendered by the Network tab:

https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/devtools/front_end/NetworkRequest.js

I'm wondering about the math in set endTime():

set endTime(x){    if (this.timing && this.timing.requestTime) {        // Check against accurate responseReceivedTime.        this._endTime = Math.max(x, this.responseReceivedTime);    } else {        // Prefer endTime since it might be from the network stack.        this._endTime = x;        if (this._responseReceivedTime > x)            this._responseReceivedTime = x;    }},

No answers just yet, but perhaps someone with more insight into what WebKit/Chromium DevTools may see this...