Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Subject: [Bug 54793] New: Socket timeout handler can delete uploaded files
 PUT upload
Date: Wed, 03 Apr 2013 06:30:50 +0000
Message-ID: <bug-54793-7868@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=54793

            Bug ID: 54793
           Summary: Socket timeout handler can delete uploaded files PUT
                    upload
           Product: Apache httpd-2
           Version: 2.5-HEAD
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_dav
          Assignee: bugs@httpd.apache.org
          Reporter: kenneth@hexad.dk
    Classification: Unclassified

When issuing a PUT request for a non-existent resource, the upload will
eventually return "201 - Created". However, if this upload is paused, or the
cable is "cut", the socket will remain open. 

Now, if another PUT request is then issued against the same resource, it can
upload a new file, but will get a "204 - No Content" response. Issuing a
PROPFIND will show the file, and issuing a GET will download the file. All
good. 

But when the original request times out, it will delete the file on the server!

This happens in production, because some German DSL subscribers have their
lines reset at least every 24-hours. When this happens, every socket is
immediately discovered as disconnected by the client, but the server only
notices absence of data. When the client retries the upload, it can succeed
(with a 204) and later disappear. If the file is large enough, the timeout
occurs during the second upload and the server responds "500 - Internal Error"
(not as bad, as the client knows it failed).

There may be similar side-effects with existing files.

The only issue I have found that appear somewhat related is #39815.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org