Three really annoying things with pyWebDAV (and one wish)
199 views
Skip to first unread message
Andreas Koten
Dec 18, 2013, 7:59:06 PM12/18/13
to pyWe...@googlegroups.com
1) The WebDav methods MOVE and COPY do not work for folders if
Server is listening on localhost. MOVE and COPY with files however
does work. Took me two days to align request headers so that they
match 100% but now they do and it still works only if not on
localhost. The log shows errors of several functions and that one
below:
"IOError: [Errno 2] No such file or directory: '/mnt/HD_a2/WebDAV/RAID/webdavtest/ahhmnb/http:/localhost:8008/RAID/webdavtest/ahh/SMSa.txt'". Note the bold part. Especially note the "localhost". When this error was reported absolutely nothing in the request header referred to localhost! I suppose that the file path is built incorrectly if localhost is involved.
2) pyWebDav seems to use memory for file transfers. This is extremely sub-optimum for a tool that obviously is targeted for minimum size systems, like e.g. my NAS. Everybody who has a system with huge memory for sure will rely on the much more bloated solutions like ownCloud, Apache, or so. On my system I better not transfer files greater than 60MB, because besides lasting eternally to complete, this would also wear down my flash memory (currently configured as swap space) very quickly. Currently I work this around by adding nginx as a proxy and let him do the PUT and GET methods. But I guess that I will loose LOCK functionality if I continue to do so, right?
3) My NAS has exactly 1MB (RAM) on /tmp. So, for sure that is not the right place for bloaty logs to go to, right? Please allow this to be set via cmdline options.
Please fix these issues. I love pyWebDav. And I would hate if I'd need to try (more) other, more bloated solutions...
And one more wish maybe: pyWebDav allows only for one user to log in, even if used with config.ini and/or mysql-login. I wrote quite some magic code around nginx to allow multiple users to login to pyWebDav (and all see different filesystems!). I think it would be nice to have such feature built in. But if interested I could also post this solution somewhere here...
best regards
ako673de
"IOError: [Errno 2] No such file or directory: '/mnt/HD_a2/WebDAV/RAID/webdavtest/ahhmnb/http:/localhost:8008/RAID/webdavtest/ahh/SMSa.txt'". Note the bold part. Especially note the "localhost". When this error was reported absolutely nothing in the request header referred to localhost! I suppose that the file path is built incorrectly if localhost is involved.
2) pyWebDav seems to use memory for file transfers. This is extremely sub-optimum for a tool that obviously is targeted for minimum size systems, like e.g. my NAS. Everybody who has a system with huge memory for sure will rely on the much more bloated solutions like ownCloud, Apache, or so. On my system I better not transfer files greater than 60MB, because besides lasting eternally to complete, this would also wear down my flash memory (currently configured as swap space) very quickly. Currently I work this around by adding nginx as a proxy and let him do the PUT and GET methods. But I guess that I will loose LOCK functionality if I continue to do so, right?
3) My NAS has exactly 1MB (RAM) on /tmp. So, for sure that is not the right place for bloaty logs to go to, right? Please allow this to be set via cmdline options.
Please fix these issues. I love pyWebDav. And I would hate if I'd need to try (more) other, more bloated solutions...
And one more wish maybe: pyWebDav allows only for one user to log in, even if used with config.ini and/or mysql-login. I wrote quite some magic code around nginx to allow multiple users to login to pyWebDav (and all see different filesystems!). I think it would be nice to have such feature built in. But if interested I could also post this solution somewhere here...
best regards
ako673de
Reply all
Reply to author
Forward
0 new messages