pimutils / pimutils/vdirsyncer
Error 415
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 185
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 1
Description
Hi,
I'm a maintainer from the project invis-server.org. We try to integrade vdirsyncer in our server-system to synchronize Kopano Calendars with other CalDAV servers.
Similar to this issue "https://github.com/pimutils/vdirsyncer/issues/502", we get the following error while synchronize from kopano to owncloud:
"415 Client Error: Unsupported Media Type for url"
In my opinion the reason for this error is, that the exported ics-files from kopano contains DOS-linebreaks.
- vdirsyncer version: 16.0 (shipped with openSUSE leap 15.0)
- If applicable, which server software (and which version) you're using
- Python 3.6.5
- openSUSE Leap 15.0
[general]
status_path = "~/.vdirsyncer/status/"
[pair my_calendars]
a = "my_calendars_local"
b = "my_calendars_remote"
collections = [["kalender", "kalender", "personal"]]
[storage my_calendars_local]
type = "caldav"
url = "https://mail.kassandra-net.loc:8443/caldav/stefan/kalender"
verify = "/etc/invis/certs/ca.crt"
username = "stefan"
password = "********"
[storage my_calendars_remote]
type = "caldav"
We can simplify this URL here as well. In theory it shouldn't matter.
url = "https://oc.xxxxxx.de/remote.php/caldav"
username = "stefan"
password = "**********"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked error.log and the supplied CalDAV configuration, then compare the failure with issue 502. Reproduce the Kopano-to-ownCloud synchronization using the reported vdirsyncer, Python, and openSUSE versions; the work is done when the 415 response is explained and the synchronization behavior or required configuration is clearly resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100