•  
      request #7110 Cannot create files via webdav
    Infos
    #7110
    Nicolas Terray (nterray)
    2017-02-03 15:37
    2014-06-24 11:17
    7127
    Details
    Cannot create files via webdav
    I can create folder, but not files.
    testlink #236

    Here are the access logs:
    212.84.62.230 - nicolas-projectadmin [24/Jun/2014:09:17:26 +0000] "PROPFIND /test-webdav/Files/P1/R2 HTTP/1.1" 207 463
    212.84.62.230 - nicolas-projectadmin [24/Jun/2014:09:17:26 +0000] "PUT /test-webdav/Files/P1/R2/Tracker_defect.xml HTTP/1.1" 500 262

    Nothing in error logs.
    Empty
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2017-02-03
    Attachments
    Empty
    References
    Referenced by request #7110

    Follow-ups

    User avatar
    This issue is not raised since a lot of Tuleap validation. I close this request.

    • Status changed from Verified to Closed
    • Reported in version cleared values: 7.2
    • Close date set to 2017-02-03
    User avatar

    Here are the logs from wireshark when I drag 'n drop a file in a webdav folder.

    First in Windows XP (works):
    4    0.000488000    10.0.2.15    192.168.2.60    HTTP    449    HEAD /gpig/Fichiers/P1/P2/blabla.txt HTTP/1.1
    6    0.961614000    192.168.2.60    10.0.2.15    HTTP    452    HTTP/1.1 404 Not Found
    8    0.978979000    10.0.2.15    192.168.2.60    HTTP    579    PUT /gpig/Fichiers/P1/P2/blabla.txt HTTP/1.1
                                                                    (Content-Length: 525)
    11   1.165667000    192.168.2.60    10.0.2.15    HTTP    463    HTTP/1.1 201 Created 
    
    Then in Windows 7 (does not work):
    76    13.341865000    10.0.2.15    192.168.2.60    HTTP    428    PROPFIND /gpig/Fichiers/P1/P6/Tracker_Import_FieldNotEmpty.xml HTTP/1.1
    80    13.468594000    192.168.2.60    10.0.2.15    HTTP/XML    810    HTTP/1.1 404 Not Found
    81    13.472978000    10.0.2.15    192.168.2.60    HTTP    413    PUT /gpig/Fichiers/P1/P6/Tracker_Import_FieldNotEmpty.xml HTTP/1.1
                                                                      (Content-Length: 0)
    84    13.607410000    192.168.2.60    10.0.2.15    HTTP    463    HTTP/1.1 201 Created
    87    13.615585000    10.0.2.15    192.168.2.60    HTTP/XML    252    LOCK /gpig/Fichiers/P1/P6/Tracker_Import_FieldNotEmpty.xml HTTP/1.1
    90    13.726864000    10.0.2.15    192.168.2.60    HTTP    381    HEAD /gpig/Fichiers/P1/P6/Tracker_Import_FieldNotEmpty.xml HTTP/1.1
    93    13.849843000    192.168.2.60    10.0.2.15    HTTP    439    HTTP/1.1 200 OK
    105    13.857509000    10.0.2.15    192.168.2.60    HTTP    56    PUT /gpig/Fichiers/P1/P6/Tracker_Import_FieldNotEmpty.xml HTTP/1.1
                                                                      (Content-Length: 12290)
    107    13.943367000    192.168.2.60    10.0.2.15    HTTP/XML    746    HTTP/1.1 403 Forbidden 

    We can see that with Windows 7, two requests are done to create a file. One PUT to create an empty file (#81: Content-Length: 0) and another one to PUT the content (#105: Content-Length: 12290).

    The Windows 7 workflow is not compatible with the current implementation.

    1. File release system does not allow to create empty files via webdav (bug due to a bad check on file creation WebDAVFRSRelease L.530, hacked to be able to run the experimentation)
    2. File release system does not allow to modify a file via webdav (thus the 403 Forbidden after the secound PUT)
    User avatar

    Dear personal diary,

    I'm desperate. For the fun I tried to upload a file to docman via webdav, using the built-in client in Windows 7. It works.

    despair

    Therefore my previous assumption about incompatibilities between built-in client and sabredav seems to be wrong.

    User avatar
    > I suspect that this comes from the fact that fileforge (updated in this commit) has not been redeployed on my dev environment.

    Confirmed. After redeployment of fileforge.pl it works locally.
    User avatar
    git bisect reveals that the issue have been introduced at commit #e1c8c096851358caa54993e7785d4cfbc587b581

    I suspect that this comes from the fact that fileforge (updated in this commit) has not been redeployed on my dev environment.

    Continuing investigations…
    User avatar
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes