https://domain name:port doesn't work

[bzmshang]

Describe the feature you'd like to request

I want to synchronize bookmarks to my Synology, so I want one that supports https://domain name:port, but currently it seems that it cannot be used if it has a port.

Describe the solution you'd like

/

Describe alternatives you've considered

/

[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]

I cannot reproduce this. It should work with a port in the server URL both for Nextcloud Bookmarks and WebDAV sync.

[bzmshang]

I cannot reproduce this. It should work with a port in the server URL both for Nextcloud Bookmarks and WebDAV sync.

After this period of testing, it is found that as long as the local web port is inconsistent with the port forwarded out, it can be used, in addition, it is also found that the path is written according to the prompt, and the synchronization will report an error, I do not know where the setting is wrong
,

[marcelklehr]

After this period of testing, it is found that as long as the local web port is inconsistent with the port forwarded out, it can be used, in addition, it is also found that the path is written according to the prompt, and the synchronization will report an error, I do not know where the setting is wrong

I'm sorry, I don't understand you. Can you give as simple as possible instructions on how to reproduce this?

for example, I did the following:

1. setup a nextcloud server, listening at localhost:8080
2. create a floccus webdav profile with https://localhost:8080/remote.php/webdav/ as server url
3. enter necessary credentials
4. sync
5. outcome: success

[bzmshang]

The “a” folder has been created in advance

Case 1：Configure the final path directly in the URL, and an error will be reported in the next step.

Case 2：Only write the root directory in the url, you can proceed to the next step

Write the final path at the bookmark path

You can create it all the way to the end of this account, but when you back it up, an error will be reported.

[marcelklehr]

Does the folder a exist? Floccus doesn't create folders for you

[marcelklehr]

Also, does accessing the webdav share work with other clients?

[bzmshang]

Sorry, I found out by what you said. It seems to be my own setting problem. Thank you very much for the answer.