[GH-ISSUE #1800] Sync fails if pipe character "|" exists in bookmark title #1202

Closed
opened 2026-02-25 22:39:18 +03:00 by kerem · 11 comments
Owner

Originally created by @vogtgbr on GitHub (Dec 15, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1800

Which version of floccus are you using?

5.4.0

How many bookmarks do you have, roughly?

3k

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

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)

No response

Describe the Bug

If there exists a pipe character
|
in the title of a bookmark like so:
<bookmark href="https://www.thingiverse.com/thing:6542198" id="5457">
<title>One-Handed Soldering Tool 2.0 | Effortless Soldering With Only One Hand by RoboticWorx - Thingiverse</title>
</bookmark>
and a sync runs and puts this in the .xbel file on the WebDav, all consecutive syncs from any device will fail with
Content-Length header of network response exceeds response Body. |
Interestingly the error message contains the character that causes the trouble.

Expected Behavior

Pipe characters in bookmark titles should not cause trouble. ;)

To Reproduce

1.) Create a bookmark with a title that contains character | (pipe)
2.) Let it sync upward so that all devices can see this bookmark
3.) Sync again to get the error message.

Debug log provided

  • I have provided a debug log file
Originally created by @vogtgbr on GitHub (Dec 15, 2024). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1800 ### Which version of floccus are you using? 5.4.0 ### How many bookmarks do you have, roughly? 3k ### 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 ### 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) _No response_ ### Describe the Bug If there exists a pipe character `|` in the title of a bookmark like so: ` <bookmark href="https://www.thingiverse.com/thing:6542198" id="5457">` ` <title>One-Handed Soldering Tool 2.0 | Effortless Soldering With Only One Hand by RoboticWorx - Thingiverse</title>` ` </bookmark>` and a sync runs and puts this in the .xbel file on the WebDav, all consecutive syncs from any device will fail with `Content-Length header of network response exceeds response Body. | ` Interestingly the error message contains the character that causes the trouble. ### Expected Behavior Pipe characters in bookmark titles should not cause trouble. ;) ### To Reproduce 1.) Create a bookmark with a title that contains character | (pipe) 2.) Let it sync upward so that all devices can see this bookmark 3.) Sync again to get the error message. ### Debug log provided - [ ] I have provided a debug log file
Author
Owner

@github-actions[bot] commented on GitHub (Dec 15, 2024):

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.
I'm Marcel and I created floccus a few years ago, maintaining it ever 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.
Note also that GitHub 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!
To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket,
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.

I look forward to working with you on this issue
Cheers 💙

<!-- gh-comment-id:2543420408 --> @github-actions[bot] commented on GitHub (Dec 15, 2024): 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. I'm Marcel and I created floccus a few years ago, maintaining it ever 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. Note also that GitHub 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! To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket, 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. I look forward to working with you on this issue Cheers :blue_heart:
Author
Owner

@marcelklehr commented on GitHub (Dec 15, 2024):

Hi @vogtgbr

I believe you are mistaken about the pipe character being the problem. I have multiple bookmarks with pipes in the title that sync fine.

The pipe character is intentionally part of the error message:
image

The error message in your case indicates that your server has a problem: Content-Length header of network response exceeds response Body.

<!-- gh-comment-id:2543699162 --> @marcelklehr commented on GitHub (Dec 15, 2024): Hi @vogtgbr I believe you are mistaken about the pipe character being the problem. I have multiple bookmarks with pipes in the title that sync fine. The pipe character is intentionally part of the error message: ![image](https://github.com/user-attachments/assets/318cb1bc-c2a6-4338-91bc-667f69540ae4) The error message in your case indicates that your server has a problem: Content-Length header of network response exceeds response Body.
Author
Owner

@vogtgbr commented on GitHub (Dec 15, 2024):

Hi Marcel,
thats really strange. I manually edited the bookmarks.xbel file on the WebDav server and changed only this single character from | to -. That did the trick, syncing worked again without problems after that. However, you are right, I discovered now that I have several titles with a pipe character myself, so this can't be the (only) reason for the problem.
I'll try to do more research on this matter and if I figure out more, I'll be happy if I may tell you about it. For now, I guess you can close this issue.
Thanks for your time!

<!-- gh-comment-id:2543921453 --> @vogtgbr commented on GitHub (Dec 15, 2024): Hi Marcel, thats really strange. I manually edited the bookmarks.xbel file on the WebDav server and changed only this single character from | to -. That did the trick, syncing worked again without problems after that. However, you are right, I discovered now that I have several titles with a pipe character myself, so this can't be the (only) reason for the problem. I'll try to do more research on this matter and if I figure out more, I'll be happy if I may tell you about it. For now, I guess you can close this issue. Thanks for your time!
Author
Owner

@marcelklehr commented on GitHub (Dec 15, 2024):

Nah, let's leave this open until we figure it out :)

<!-- gh-comment-id:2543940981 --> @marcelklehr commented on GitHub (Dec 15, 2024): Nah, let's leave this open until we figure it out :)
Author
Owner

@marcelklehr commented on GitHub (Dec 16, 2024):

I manually edited the bookmarks.xbel file on the WebDav server and changed only this single character from | to -.

It may have been just the edit that made it work?

<!-- gh-comment-id:2546277334 --> @marcelklehr commented on GitHub (Dec 16, 2024): > I manually edited the bookmarks.xbel file on the WebDav server and changed only this single character from | to -. It may have been just the edit that made it work?
Author
Owner

@vogtgbr commented on GitHub (Dec 17, 2024):

Jep, I didn't do anything else and I don't know why it started working again. Maybe the time stamp of bookmarks.xbel was the reason? It must have changed when I edited it.

<!-- gh-comment-id:2547491231 --> @vogtgbr commented on GitHub (Dec 17, 2024): Jep, I didn't do anything else and I don't know why it started working again. Maybe the time stamp of bookmarks.xbel was the reason? It must have changed when I edited it.
Author
Owner

@shirocko commented on GitHub (Jan 3, 2025):

Hi. I got the same error and can reproduce it again and again, but for me the error occurs at the tab synchronisation.
The following error occurs, when I have the startpage of t-online.de open as a tab.
image
The title of the page always has a "|" in the name and that seems to block or stop the synchronisation.
If I navigate to a sub page of t-online.de, when the sync is working fine.
image

<!-- gh-comment-id:2568810986 --> @shirocko commented on GitHub (Jan 3, 2025): Hi. I got the same error and can reproduce it again and again, but for me the error occurs at the tab synchronisation. The following error occurs, when I have the startpage of [t-online.de](https://t-online.de) open as a tab. ![image](https://github.com/user-attachments/assets/485ea653-66e4-4208-9156-072dcd4569f3) The title of the page always has a "|" in the name and that seems to block or stop the synchronisation. If I navigate to a sub page of [t-online.de](https://t-online.de), when the sync is working fine. ![image](https://github.com/user-attachments/assets/b25dba2e-8ee0-424c-ac24-10420d1524fc)
Author
Owner

@marcelklehr commented on GitHub (Jan 3, 2025):

Hi @shirocko
That's curious. Are you also using WebDAV to sync? Can you check your server logs for the 500 error?

<!-- gh-comment-id:2568858793 --> @marcelklehr commented on GitHub (Jan 3, 2025): Hi @shirocko That's curious. Are you also using WebDAV to sync? Can you check your server logs for the 500 error?
Author
Owner

@shirocko commented on GitHub (Jan 3, 2025):

Hi @marcelklehr
I am not using webdav, but I use a self hosted nextcloud instance based on docker and in the logs I only see the same error, as in the debug logs from the floccus addon.

Output debug.log addon:

Syncing failed with E019: HTTP status 500. Failed PUT request. Check your server configuration and log.

Output apache log of nextcloud docker container:

bookmarksync [03/Jan/2025:20:49:36 +0000] "PUT /index.php/apps/bookmarks/public/rest/v2/bookmark/3763 HTTP/1.1" 500 1930 "-" "Mozilla..."

When the sync is working the apache log line looks the following:

bookmarksync [03/Jan/2025:20:49:47 +0000] "PUT /index.php/apps/bookmarks/public/rest/v2/bookmark/3763 HTTP/1.1" 200 2252 "-" "Mozilla...

<!-- gh-comment-id:2569801918 --> @shirocko commented on GitHub (Jan 3, 2025): Hi @marcelklehr I am not using webdav, but I use a self hosted nextcloud instance based on docker and in the logs I only see the same error, as in the debug logs from the floccus addon. Output debug.log addon: > Syncing failed with E019: HTTP status 500. Failed PUT request. Check your server configuration and log. Output apache log of nextcloud docker container: > bookmarksync [03/Jan/2025:20:49:36 +0000] "PUT /index.php/apps/bookmarks/public/rest/v2/bookmark/3763 HTTP/1.1" 500 1930 "-" "Mozilla..." When the sync is working the apache log line looks the following: > bookmarksync [03/Jan/2025:20:49:47 +0000] "PUT /index.php/apps/bookmarks/public/rest/v2/bookmark/3763 HTTP/1.1" 200 2252 "-" "Mozilla...
Author
Owner

@marcelklehr commented on GitHub (Jan 4, 2025):

@shirocko Please open a new ticket for this, as this ticket is about webdav. Also, can you check the nextcloud log for errors?

<!-- gh-comment-id:2570134912 --> @marcelklehr commented on GitHub (Jan 4, 2025): @shirocko Please open a new ticket for this, as this ticket is about webdav. Also, can you check the nextcloud log for errors?
Author
Owner

@github-actions[bot] commented on GitHub (Jan 14, 2026):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:3747159740 --> @github-actions[bot] commented on GitHub (Jan 14, 2026): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
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#1202
No description provided.