Dear WWWOFFLE professionals, with WWWOFFLE 2.6a, recently, with my
ISP, I get lots of
The remote host failed to send the reply within the timeout period
from WWWOFFLE. Turning off WWWOFFLE, one sees that maybe if WWWOFFLE
tried longer or something, it might have got thru:
$ wget -Y off http://www.useit.com/alertbox/
--00:46:27-- http://www.useit.com/alertbox/
=> `index.html.1'
Resolving www.useit.com... done.
Connecting to www.useit.com[216.122.217.249]:80... connected.
HTTP request sent, awaiting response...
Read error (Connection reset by peer) in headers.
Retrying.
--00:46:30-- http://www.useit.com/alertbox/
(try: 2) => `index.html.1'
Connecting to www.useit.com[216.122.217.249]:80... connected.
HTTP request sent, awaiting response...
Read error (Connection reset by peer) in headers.
Retrying.
--00:46:33-- http://www.useit.com/alertbox/
(try: 3) => `index.html.1'
Connecting to www.useit.com[216.122.217.249]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 17,353 [text/html]
100%[=====================================================>] 17,353 10.36K/s
ETA 00:00
00:46:35 (10.36 KB/s) - `index.html.1' saved [17353/17353]
P.S. I cannot do
echo 1 > /proc/sys/net/ipv4/ecn
on my
linux 2.2.17-21mdk Oct 5 13:16:08 CEST 2000 i586
I don't know what needs adjusting. All I know is that about 1/2 of
the web times out on the initial click :-(
P.S. I didn't really type "WWWOFFLE" over and over as above. I use
dabbrev-expand of emacs.
--
http://www.geocities.com/jidanni/ Tel+886-4-25854780
