- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 04 Mar 2009 14:04:10 +0000
- To: www-validator-cvs@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4985
Olivier Thereaux <ot@w3.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.5
--- Comment #3 from Olivier Thereaux <ot@w3.org> 2009-03-04 14:04:09 ---
(In reply to comment #2)
> therefore, I agree we could lower the link checker's default timeout value to,
> say, 20 or 30 seconds.
In my test instance of the link checker, I have the default timeout set to 20
seconds. I just found a strange (not documented AFAICT) behavior of LWP. See
this output:
Checking link http://jtc1sc36.org/doc/36N1141.pdf
HEAD http://jtc1sc36.org/doc/36N1141.pdf fetched in 41.01s
Checking link http://jtc1sc36.org/doc/36N1142.pdf
HEAD http://jtc1sc36.org/doc/36N1142.pdf fetched in 21.00s
Both resources are later reported as timing out. Note that for the first
resource, LWP waited twice the configured time before it timed out.
This doubling would actually explain why apache (timeout 120) currently times
out before the link checker (currenty timeout 60 in the production version)
does. Browsers typically timeout at 300 seconds, so not a problem.
I suggest we switch the default timeout value to 30s in the upcoming 4.5
release. Users checking very slow servers on the commandline can override that
setup.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 4 March 2009 14:04:18 UTC