From 28cd3b215d9ec6023ed4a97e10ba2ded11af5fe2 Mon Sep 17 00:00:00 2001
From: davidsarah <>
Date: Sun, 13 Jun 2010 19:13:17 +0000
Subject: [PATCH] WinSCP workaround

[Imported from Trac: page SftpFrontend, version 31]
---
 SftpFrontend.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/SftpFrontend.md b/SftpFrontend.md
index 9a811cb..4553a32 100644
--- a/SftpFrontend.md
+++ b/SftpFrontend.md
@@ -11,7 +11,7 @@ In practice, that means you can run the Tahoe-LAFS gateway locally on the same m
 
 ### General compatibility issues
 
-Before uploading a file to a Tahoe filesystem, the whole file has to be available. This means that the upload can only start when the file has been closed in the SFTP session. Particularly when writing large files, the client may time out between sending the close request and receiving the response (ticket #1041). This is known to be a problem for at least the WinSCP client, which has a close timeout of 15 seconds.
+Before uploading a file to a Tahoe filesystem, the whole file has to be available. This means that the upload can only start when the file has been closed in the SFTP session. Particularly when writing large files, the client may time out between sending the close request and receiving the response (ticket #1041). This is known to be a problem for at least the WinSCP client, which has a default close timeout of 15 seconds. In the case of WinSCP this can be worked around by setting WinSCP -> Connection -> Timeouts to 6000 seconds (the maximum allowed); other clients with this problem may have similar settings.
 
 In the period after the close but before the upload has finished, the closed file may not appear in directory listings, or may appear with an incorrect modification time.