starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-26 14:45:59 +03:00

[GH-ISSUE #1928] Sync failure due to missing Depth header in PROPFIND #1290

New issue

Closed

opened 2026-02-25 22:39:34 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 22:39:34 +03:00

Owner

Originally created by @G-Huber on GitHub (Apr 30, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1928

Which version of floccus are you using?

5.5.2

How many bookmarks do you have, roughly?

200

Are you using other means to sync bookmarks in parallel to floccus?

Sync method

WebDAV

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Firefox 138

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

Lighttpd

Describe the Bug

Since roughly 3 Weeks ago (I suspect the 5.5.0 update) Floccus outputs:
E042: Remote bookmarks file size could not be retrieved. It is impossible to verify that the bookmarks file was downloaded in full. If this error persists please contact the server administrator.
Logs

Floccus logs say:

2025-04-30T04:36:15.908Z Starting sync process for account <acc>@<mydomain>
2025-04-30T04:36:15.916Z onSyncStart: begin
2025-04-30T04:36:15.919Z ###server###webdav/browsersync/tabs_work_notebook.xbel.lock
2025-04-30T04:36:16.031Z Setting lock: ###server###webdav/browsersync/tabs_work_notebook.xbel.lock
2025-04-30T04:36:16.115Z Error getting file size: E018: Couldn't authenticate with the server.
2025-04-30T04:36:16.116Z Syncing failed with E042: Remote bookmarks file size could not be retrieved. It is impossible to verify that the bookmarks file was downloaded in full. If this error persists please contact the server administrator.
2025-04-30T04:36:16.122Z onSyncFail
2025-04-30T04:36:16.122Z Freeing lock: ###server###webdav/browsersync/tabs_work_notebook.xbel.lock

lighttpd logs say:

[30/Apr/2025:04:36:15 +0000] <mydomain> <clientIP> <acc> "GET /webdav/browsersync/tabs_work_notebook.xbel.lock HTTP/2.0" 404 341 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0"
[30/Apr/2025:04:36:16 +0000] <mydomain> <clientIP> <acc> "PUT /webdav/browsersync/tabs_work_notebook.xbel.lock HTTP/2.0" 201 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0"
[30/Apr/2025:04:36:16 +0000] <mydomain> <clientIP> <acc> "GET /webdav/browsersync/tabs_work_notebook.xbel HTTP/2.0" 200 2693 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0"
[30/Apr/2025:04:36:16 +0000] <mydomain> <clientIP> <acc> "PROPFIND /webdav/browsersync/tabs_work_notebook.xbel HTTP/2.0" 403 341 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0"
[30/Apr/2025:04:36:16 +0000] <mydomain> <clientIP> <acc> "DELETE /webdav/browsersync/tabs_work_notebook.xbel.lock HTTP/2.0" 204 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0"

So from this the culprit seems to be the 403ing PROPFIND request.

Looking at the request in FF Devtools

PROPFIND /webdav/browsersync/tabs_work_notebook.xbel HTTP/2
Host: <mydomain>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0
Accept: */*
Accept-Language: de,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate, br, zstd
Authorization: Basic cGFuZGE6ITBGbG9yaWFu
Origin: moz-extension://013fee59-e309-4ed3-b2ca-ba4e683e0191
DNT: 1
Connection: keep-alive
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
Priority: u=4
Pragma: no-cache
Cache-Control: no-cache
TE: trailers

Depth header is missing!

https://www.rfc-editor.org/rfc/rfc4918#section-9.1

A client MUST submit a Depth header with a value of "0", "1", or "infinity" with a PROPFIND request.

Expected Behavior

Sync successfully completing

To Reproduce

Happens every time with lighttpd webdav

Debug log provided

I have provided a debug log file

Originally created by @G-Huber on GitHub (Apr 30, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1928 ### Which version of floccus are you using? 5.5.2 ### How many bookmarks do you have, roughly? 200 ### Are you using other means to sync bookmarks in parallel to floccus? no ### Sync method WebDAV ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Firefox 138 ### Which version of Nextcloud Bookmarks are you using? (if relevant) _No response_ ### Which version of Nextcloud? (if relevant) _No response_ ### What kind of WebDAV server are you using? (if relevant) Lighttpd ### Describe the Bug Since roughly 3 Weeks ago (I suspect the 5.5.0 update) Floccus outputs: `E042: Remote bookmarks file size could not be retrieved. It is impossible to verify that the bookmarks file was downloaded in full. If this error persists please contact the server administrator.` Logs Floccus logs say: ``` 2025-04-30T04:36:15.908Z Starting sync process for account <acc>@<mydomain> 2025-04-30T04:36:15.916Z onSyncStart: begin 2025-04-30T04:36:15.919Z ###server###webdav/browsersync/tabs_work_notebook.xbel.lock 2025-04-30T04:36:16.031Z Setting lock: ###server###webdav/browsersync/tabs_work_notebook.xbel.lock 2025-04-30T04:36:16.115Z Error getting file size: E018: Couldn't authenticate with the server. 2025-04-30T04:36:16.116Z Syncing failed with E042: Remote bookmarks file size could not be retrieved. It is impossible to verify that the bookmarks file was downloaded in full. If this error persists please contact the server administrator. 2025-04-30T04:36:16.122Z onSyncFail 2025-04-30T04:36:16.122Z Freeing lock: ###server###webdav/browsersync/tabs_work_notebook.xbel.lock ``` lighttpd logs say: ``` [30/Apr/2025:04:36:15 +0000] <mydomain> <clientIP> <acc> "GET /webdav/browsersync/tabs_work_notebook.xbel.lock HTTP/2.0" 404 341 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0" [30/Apr/2025:04:36:16 +0000] <mydomain> <clientIP> <acc> "PUT /webdav/browsersync/tabs_work_notebook.xbel.lock HTTP/2.0" 201 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0" [30/Apr/2025:04:36:16 +0000] <mydomain> <clientIP> <acc> "GET /webdav/browsersync/tabs_work_notebook.xbel HTTP/2.0" 200 2693 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0" [30/Apr/2025:04:36:16 +0000] <mydomain> <clientIP> <acc> "PROPFIND /webdav/browsersync/tabs_work_notebook.xbel HTTP/2.0" 403 341 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0" [30/Apr/2025:04:36:16 +0000] <mydomain> <clientIP> <acc> "DELETE /webdav/browsersync/tabs_work_notebook.xbel.lock HTTP/2.0" 204 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0" ``` So from this the culprit seems to be the 403ing PROPFIND request. Looking at the request in FF Devtools ``` PROPFIND /webdav/browsersync/tabs_work_notebook.xbel HTTP/2 Host: <mydomain> User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:138.0) Gecko/20100101 Firefox/138.0 Accept: */* Accept-Language: de,en-US;q=0.7,en;q=0.3 Accept-Encoding: gzip, deflate, br, zstd Authorization: Basic cGFuZGE6ITBGbG9yaWFu Origin: moz-extension://013fee59-e309-4ed3-b2ca-ba4e683e0191 DNT: 1 Connection: keep-alive Sec-Fetch-Dest: empty Sec-Fetch-Mode: cors Sec-Fetch-Site: same-origin Priority: u=4 Pragma: no-cache Cache-Control: no-cache TE: trailers ``` Depth header is missing! [https://www.rfc-editor.org/rfc/rfc4918#section-9.1](https://www.rfc-editor.org/rfc/rfc4918#section-9.1) > A client MUST submit a Depth header with a value of "0", "1", or "infinity" with a PROPFIND request. ### Expected Behavior Sync successfully completing ### To Reproduce Happens every time with lighttpd webdav ### Debug log provided - [x] I have provided a debug log file

kerem

2026-02-25 22:39:34 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:39:34 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 30, 2025):

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

@github-actions[bot] commented on GitHub (Apr 30, 2025): Hello :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers :blue_heart:

kerem commented

2026-02-25 22:39:34 +03:00

Author

Owner

@marcelklehr commented on GitHub (Apr 30, 2025):

Damn, you're spot on! Thank you for this report! It seems Nextcloud might be more forgiving than other implementors

@marcelklehr commented on GitHub (Apr 30, 2025): Damn, you're spot on! Thank you for this report! It seems Nextcloud might be more forgiving than other implementors

kerem commented

2026-02-25 22:39:34 +03:00

Author

Owner

@G-Huber commented on GitHub (May 1, 2025):

Thank you for developing floccus! :)

@G-Huber commented on GitHub (May 1, 2025): Thank you for developing floccus! :)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/floccus#1290

No description provided.

Rows
Columns