mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #153] XBEL sync not working with owncloud (Origin header=null) #142
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#142
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 @minj on GitHub (Aug 25, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/153
Software versions
Sync settings
WebDAV URL: https://my.domain.tld/my_prefix/remote.php/webdav/
Bookmarks file path: bookmarks.xbel
Steps to reproduce
Expected outcome
bookmarks.xbel should have been saved
Actual outcome
bookmarks.xbel was not saved
Initially I created an empty bookmarks.xbel on my server and the sync would halt due to
Account.js:171 Syncing failed with Cannot read property 'childNodes' of undefined. This indicates read access is working with my settings, only the file was invalid.Then I removed it, and I now see log messages for bookmark parsing (COMPARE, CREATE etc)
However, the process fails at PUT/DELETE requests for bookmarks.xbel and bookmarks.xbel.lock with HTTP500.
Example log from my owncloud instance:
Looking at this @ the source:
github.com/owncloud/core@d5836485ac/apps/dav/lib/Connector/Sabre/CorsPlugin.php (L98)It seems owncloud expects the Origin header to be missing or parsable, but
nullisn't.AFAIK, it is impossible to set with fetch since it's CORS-related :(
Can this be solved on your end or do I need to file this on their repo?
@jlbprof commented on GitHub (Aug 25, 2018):
Hmm, I have never seen that. I am interested to see if the problem is
Owncloud specific or not. You have the latest Owncloud as far as I can
tell. I do not experience the problem with the latest Nextcloud.
Nextcloud is a fork of Owncloud, but they both use SabreDAV under the
hood for WebDAV support, so I would expect that they would perform the same.
I just ran across this document:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
It seems related. I do not see anything that specifies the "Origin"
header, but it does seem like it might be controlled by this directive. I
do not know if the app sets these directives or it is set in the browser or
what.
Julian
On Sat, Aug 25, 2018 at 4:51 AM LA-MJ notifications@github.com wrote:
@minj commented on GitHub (Aug 25, 2018):
Re:headers, see https://developer.mozilla.org/en-US/docs/Glossary/Forbidden_header_name
I am not sure, how much of this applies in extensions.
If you take a look at https://github.com/nextcloud/server/tree/master/apps/dav/lib/Connector/Sabre
there is CorsPlugin is nextcloud at all.
I'll try adding
credentials=includeormode=no-cors|same-originfor all fetch requests in floccus as a test. I have no other ideas at this point@marcelklehr commented on GitHub (Aug 25, 2018):
I thought the same thing. Still might not work. Could you test in firefox as well to see if this is a bug in chrome?
@minj commented on GitHub (Aug 25, 2018):
I was not able to remove Origin header in chrome.
Firefox is sending
moz-extension://fe404075-445f-4b57-8f4b-0a96fe99639cas originThis fails as well with "Only http based URLs supported".
I will file a bug report @ owncloud
@minj commented on GitHub (Aug 25, 2018):
nevermind, it's already fixed @ owncloud/core#32120 😄
@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.