Hi,
following scenario:
client -> 100MBit -> wwwoffle -> 2k -> server
The clients sends a file with http POST to the server. This happens:
time 0s: Client sends the file to wwwoffle
time 1s: wwwoffle starts sending the file to the server
time 120s: wwwoffle sends the clients the message "remote host error" and
kills the link to the server
I found socket-timeout with 120 seconds in my wwwoffle.conf. So I think
after wwwoffle received the file (i.e. the POST request) it starts
sending the file to the server and starts a timer of 120s for the
connection to the client. But the client will not talk to wwwoffle,
because it waits for an acknowledgement from wwwoffle that its data
reached the server. After 120s the timeout takes place and kills the
connection to the client, because in the last 120 secound no data crossed
the line. But this is not the fault of the client. It's simply the result
of the slow uplink.
So I will try now increasing the value of socket-timeout, but this is not
a sollution, because I have no upper bound. A 2MB file need nearly 20
minutes to send, which requires a timeout of 1000 second, which drives
the meaning of socket-timeout ad absurdum.
Better solutions?
Regards, Jörg.
PS: I use wwwoffle 2.8e.
--
"Politics is for the moment, equations are forever"
-- Albert Einstein
