Question about ERR_TIMED_OUT

[Oscar (Ang) Pan]

Hi,

I'm trying to make a xhr inside a component extension. The xhr has a time out 20 seconds and a timeout handler. When I inspect it under chrome://net-internals, I'm getting this event log,

1911: URL_REQUEST

(sensitive url, so I removed it)

Start Time: 2013-02-15 11:43:55.020

t=1360957435020 [st=    0] +REQUEST_ALIVE  [dt=30145]
t=1360957435020 [st=    0]   +URL_REQUEST_START_JOB  [dt=30144]
                              --> load_flags = 67174528 (ENABLE_LOAD_TIMING | MAYBE_USER_GESTURE | VERIFY_EV_CERT)
                              --> method = "POST"
                              --> priority = 2
                              --> upload_id = "0"
                              --> url = "(sensitive url, so I removed it)"
t=1360957435021 [st=    1]      HTTP_CACHE_GET_BACKEND  [dt=0]
t=1360957435021 [st=    1]      HTTP_STREAM_REQUEST  [dt=30143]
t=1360957465164 [st=30144]   -URL_REQUEST_START_JOB
                              --> net_error = -7 (ERR_TIMED_OUT)
t=1360957465165 [st=30145] -REQUEST_ALIVE
                            --> net_error = -7 (ERR_TIMED_OUT)

However, my xhr's timeout handler is never triggered. And if I tried to resend the request by clicking on the trigger button, my xhr's abort handler is triggered.

I have no idea about ERR_TIMED_OUT vs xhr's timeout. Could someone help me with this?

Thanks a lot!

Oscar

[William Chan (陈智昌)]

That's most likely a TCP connect() timeout. I'd need to know your sensitive URL and probably get a packet dump to explain why. It says the timeout happened after 30s, which is our transport connect job timeout that wraps our TCP connect().

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
 
 
 

[Oscar (Ang) Pan]

The url is our apiary api frontend and is definetly working. The issue is we are not directly connect to public network or google network. Instead, we have a wireless AP set up by our partner and that AP connects to their proxy server. All our request will go to their proxy first and then reach the sensitive url. This environment setup tries to simulate the real situation we have in prod. So my purpose is just trying to handle such kind of failure using our extension. I just don't know how my code can be notified when "ERR_TIMED_OUT" happened. Seems it's not a xhr timeout. Do you have any ideas?

[William Chan (陈智昌)]

I don't know why the xhr timeout isn't working. That's implemented at the WebKit level. A quick look shows though:

https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/WebCore/xml/XMLHttpRequest.cpp&q=XmlHttpRequest.cpp&sq=package:chromium&l=340

https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/WebKit/chromium/features.gypi&q=ENABLE_XHR_TIMEOUT&sq=package:chromium&l=136

Seems like Chromium doesn't support the XHR timeout. That's probably why. I don't know why we don't.

[Ryan Sleevi]

On Fri, Feb 15, 2013 at 12:16 PM, William Chan (陈智昌)
<will...@chromium.org> wrote:
> I don't know why the xhr timeout isn't working. That's implemented at the
> WebKit level. A quick look shows though:
> https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/WebCore/xml/XMLHttpRequest.cpp&q=XmlHttpRequest.cpp&sq=package:chromium&l=340
> https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/WebKit/chromium/features.gypi&q=ENABLE_XHR_TIMEOUT&sq=package:chromium&l=136
>
> Seems like Chromium doesn't support the XHR timeout. That's probably why. I
> don't know why we don't.

https://groups.google.com/a/chromium.org/d/topic/chromium-dev/YidnX-WUwDI/discussion

[Pierre]

2015-11-07

I've got the same problem when I choose another ISP. I thought I would have only to put my new ID and password, but it wasn't the case.

I have an ADSL modem with a dry loop. To resolve the problem ERR_TIMED_OUT, I had to ajusted the MTU ans MRU values. I put 1458 rather than 1492, which is the default value. It works for me. You can do it by yourself (test/error), or ask your ISP for the values. Good luck.