-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apple calendar server discover issue #457
Comments
The server appears to think you're unauthenticated. Could you try setting |
Hello Markus, that worked for me, you can close the ticket, except you want to Thank you On 30.05.2016 18:20, Markus Unterwaditzer wrote:
|
We might change the default to |
server:
apple calendarserver 4.2-1~tree.se on debian wheezy
(this is not by choice, I have to get it working - somehow)
client:
debian jessie
vdirsyncer 0.11.0
clientpython 2.7.9-2
config:
[general]
status_path = ~/.vdirsyncer/status/
python2 = true
[pair muman_contacts]
a = muman_contacts_local
b = muman_contacts_remote
collections = ["from a", "from b"]
metadata = ["displayname"]
conflict_resolution = "b wins"
[storage muman_contacts_local]
type = filesystem
path = ~/dav-sync/contacts/
fileext = .vcf
[storage muman_contacts_remote]
type = carddav
url = https://agenda.architektur.tu-darmstadt.de/
or
url = https://agenda.architektur.tu-darmstadt.de
same result
username = muman
password = password
[pair muman_calendar]
a = muman_calendar_local
b = muman_calendar_remote
collections = ["from a", "from b"]
metadata = ["displayname", "color"]
conflict_resolution = "b wins"
[storage muman_calendar_local]
type = filesystem
path = ~/dav-sync/calendars/
fileext = .ics
[storage muman_calendar_remote]
type = caldav
url = https://agenda.architektur.tu-darmstadt.de/
or
url = https://agenda.architektur.tu-darmstadt.de
same result
username = muman
password = password
vdirsyncer_debug-log.txt
The issue seems to be those '200 - permanently moved' answers. Several client libs I tried can not handle this server behavior.
The text was updated successfully, but these errors were encountered: