lighttpd webdav fails w/ joplin (fix avail upstream)

[Imre Péntek]

Hello,

as far as I can tell joplin is unable to sync to my webdav due to this issue:

$ litmus ${WEBDAVURL} ${WEBDAVUSER} ${WEBDAVPASS}
-> running `basic':
 0. init.................. pass
 1. begin................. pass
 2. options............... pass
 3. put_get............... pass
 4. put_get_utf8_segment.. pass
 5. put_no_parent......... pass
 6. mkcol_over_plain...... pass
 7. delete................ pass
 8. delete_null........... pass
 9. delete_fragment....... pass
10. mkcol................. pass
11. mkcol_again........... pass
12. delete_coll........... pass
13. mkcol_no_parent....... pass
14. mkcol_with_body....... pass
15. finish................ pass
<- summary for `basic': of 16 tests run: 16 passed, 0 failed. 100.0%
-> running `copymove':
 0. init.................. pass
 1. begin................. pass
 2. copy_init............. pass
 3. copy_simple........... pass
 4. copy_overwrite........ pass
 5. copy_nodestcoll....... pass
 6. copy_cleanup.......... pass
 7. copy_coll............. pass
 8. copy_shallow.......... pass
 9. move.................. pass
10. move_coll............. pass
11. move_cleanup.......... pass
12. finish................ pass
<- summary for `copymove': of 13 tests run: 13 passed, 0 failed. 100.0%
-> running `props':
 0. init.................. pass
 1. begin................. pass
 2. propfind_invalid...... pass
 3. propfind_invalid2..... FAIL (PROPFIND with invalid namespace declaration in body (see FAQ) got 207 response not 400)
 4. propfind_d0........... pass
 5. propinit.............. pass
 6. propset............... pass
 7. propget............... pass
 8. propextended.......... pass
 9. propmove.............. pass
10. propget............... pass
11. propdeletes........... pass
12. propget............... pass
13. propreplace........... pass
14. propget............... pass
15. propnullns............ pass
16. propget............... pass
17. prophighunicode....... pass
18. propget............... pass
19. propremoveset......... pass
20. propget............... pass
21. propsetremove......... pass
22. propget............... pass
23. propvalnspace......... pass
24. propwformed........... pass
25. propinit.............. pass
26. propmanyns............ pass
27. propget............... pass
28. propcleanup........... pass
29. finish................ pass
<- summary for `props': of 30 tests run: 29 passed, 1 failed. 96.7%
See debug.log for network/debug traces.

further reading:
https://discourse.joplinapp.org/t/joplin-webdav-reupload-fails/27516/6
https://github.com/laurent22/joplin/issues/3457#issuecomment-1152977681
allegedly this bug is fixed in 1.4.64
thank you in advance for the fix

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: lighttpd-mod-webdav 1.4.63-1ubuntu3
Uname: Linux 4.19.49v6v7-aufs armv7l
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: armhf
CasperMD5CheckResult: unknown
Date: Fri Sep 23 21:46:49 2022
ImageMediaBuild: 20220419
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: lighttpd
UpgradeStatus: No upgrade log present (probably fresh install)

[Imre Péntek (pentek-imre)]

maybe it's this patch, but maybe not: https://github.com/lighttpd/lighttpd1.4/commit/8a535e7e064b0c33c3b60a92df88b349d79b94c2

[Imre Péntek (pentek-imre)]

I use joplin-desktop 2.8.8 from a snap package on an x64 machine

[gstrauss (gstrauss)]

You should be using a snap of lighttpd 1.4.67, the latest lighttpd release as I write this. If there is no snap of lighttpd 1.4.67, maybe you should consider using a distro that maintains its software, i.e. just about anything other than Ubunutu.

(I am a developer of lighttpd and wrote lighttpd mod_webdav but it is often a waste of time trying to get Ubuntu to pick up fixes. Just preparing you for this bug to inevitably be ignored. Pathetic, but likely.)

[gstrauss (gstrauss)]

lighttpd 1.4.64 (released Jan 2022) fixes https://github.com/laurent22/joplin/issues/6450 WebDav sync error

[Imre Péntek (pentek-imre)]

https://discourse.joplinapp.org/t/joplin-webdav-reupload-fails/27516/12

[gstrauss (gstrauss)]

> https://discourse.joplinapp.org/t/joplin-webdav-reupload-fails/27516/12

There is not much to "discuss".

How many different ways do you want me to tell you that you are wasting your time troubleshooting something that has already been fixed? (because you use Ubuntu, which is negligent in maintenance since Ubuntu considers "maintenance" and "do nothing" to be equivalent in many cases.)

https://github.com/laurent22/joplin/issues/1228
https://github.com/laurent22/joplin/issues/3457

In the second one (https://github.com/laurent22/joplin/issues/3457) I asked for more info, which I did not get. That was Jul 2020.

In Dec 2021, someone reported info to the lighttpd developers in https://redmine.lighttpd.net/boards/3/topics/10193, and a patch was provided the *same day*, and released in lighttpd 1.4.64 a month later.

You've already quote me (in the discourse)
from https://github.com/laurent22/joplin/issues/3457
> This issue was fixed in lighttpd 1.4.64 (and would have been fixed sooner if reported to lighttpd developers sooner).
> (nobody responded to my post above on 29 July 2020)

and repeated in https://github.com/laurent22/joplin/issues/6450 where I repeated:

Even though the bug was fixed in Jan 2022 in lighttpd 1.4.64, someone posted https://github.com/laurent22/joplin/issues/6450 in Apr 2022, and when asked if anyone tested with lighttpd 1.4.64, someone responded that joplin does work with lighttpd 1.4.64.

You're still using lighttpd 1.4.63 over 9 months after lighttpd 1.4.64 was released (and subsequently, lighttpd 1.4.65, lighttpd 1.4.66, and lighttpd 1.4.67).

Latest lighttpd release as I write this is lighttpd 1.4.67. Maybe Ubuntu will pick up lighttpd 1.4.67 because it fixes a CVE. More likely they'll (eventually) backport just the patch to fix the CVE.

[Imre Péntek (pentek-imre)]

hello, can I get an update on this one? rclone webdav is working great for me, and I don't want to try to switch to lighttpd just to realize it still doesn't work. Thank you in advance.

[gstrauss (gstrauss)]

> hello, can I get an update on this one?

I question your ability to comprehend any response since it seems you have not bothered to check package info.

https://packages.ubuntu.com/search?keywords=lighttpd

[gstrauss (gstrauss)]

lunar (23.04) (web): fast webserver with minimal memory footprint [universe]
1.4.67-1ubuntu2: amd64 arm64 armhf ppc64el riscv64 s390x