* Andrew M. Bishop <[EMAIL PROTECTED]> [26.10.06 04:39]: > Felix Karpfen <[EMAIL PROTECTED]> writes:
SNIP > > > because of delays caused by system load at the remote host, I > > got a time-out message from WWWOFFLE instead of the expected > > acknowledgement of the purchase. Consequently I was left totally in > > the dark about the <arrival | non-arrival> of my purchase request. > > > > Looking at the contents of the WWWOFFLE cache subsequently (when > > offline), it turned out that the remote host did receive the request and > > send an acknowledgement; the reply made it to the cache, but not to the > > screen of my computer. > > SNIP > > The third timeout is the amount of time that WWWOFFLE will wait after > trying to open the connection to the server ***for the first data to > arrive.*** If no data arrives in the given time then WWWOFFLE will give > up. > > > In your case I think that the first one is the problem. You made the > connection to the server (since you found the message in the cache) so > it was not the other two timeouts that caused the problem since they > both relate to the start of the connection. > Thank you for the advice. I was speculating that "connect-timeout" might also be relevant. I am unfamiliar with the "nuts and bolts" of the routines at the remote server. But it often happens that purchase-confirmations are handled via https; I thought that this might involve a different server. I shall find out next time that I try to order some coffee beans! Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA)
