HTTP status 414 error when syncing bookmarklet to Nextcloud Snap

[ImintA2]

Which version of floccus are you using?

5.1.2

How many bookmarks do you have, roughly?

500

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

No

Sync method

Nextcloud Bookmarks

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

Catsxp 4.5.1

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

13.1.3

Which version of Nextcloud? (if relevant)

27.1.9

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

No response

Describe the Bug

I have some bookmarklets, and they're causing the syncing process to stuck in a loop of retrying with error:
2024-05-16T11:28:07.924Z Syncing failed with E019: HTTP status 414. Failed GET request. Check your server configuration and log.

From my understanding, this happens because Apache server has a default LimitRequestLine set to 8190.
It'd throw a Request-URI Too Long error if a GET Request exceed the limit.

You could say this is a server configuration issue because one should be able to solve this by increasing the LimitRequestLine value, however there's no way to edit this setting in the Snap version of Nextcloud which is what I'm using so I'm out of luck.

Expected Behavior

Hopefully an option to ignore items that are too long so the syncing process won't stuck in a retry loop.
Or an option to exclude bookmarklet also works.

To Reproduce

Attempt to sync a bookmark/tab that's too long (>8190 characters) to a Nextcloud installed with Snap.

Debug log provided

• I have provided a debug log file

[github-actions]

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 and have been 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!
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 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 💙

[marcelklehr]

Ah, that's a nice catch. I have a fix for this in mind already.

[marcelklehr]

Should be fixed in v5.1.3