mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #219] Webdav: server URL isn't normalized #210
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#210
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @eleksis on GitHub (Dec 29, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/219
Hi,
I'm trying to make floccus work with webdav on my shared hosting.
They are using port 2078 for webdav. And it looks like floccus ignores port when i pass it as part of url in settings.
WebDAV URL:
https://my-domain.com:2078
The error I get:
Network error: Check your network connection and your account details
Can someone confirm this is not supported?
And I can probably implement this, if I get some directions...
@marcelklehr commented on GitHub (Dec 29, 2018):
Mmh. This should be supported.
But I just checked and noticed that the webdav adapter doesn't normalize urls, so it might work if you append a slash.
@eleksis commented on GitHub (Dec 29, 2018):
Yes, that did the trick. Thank you.
@jlbprof commented on GitHub (Dec 30, 2018):
Yes you will need to append a slash.
On Sat, Dec 29, 2018 at 3:16 PM Vito notifications@github.com wrote:
@github-actions[bot] commented on GitHub (Mar 21, 2023):
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.