-
Notifications
You must be signed in to change notification settings - Fork 46
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
Accessing google address book #16
Comments
I found another link (German) saying, that the google caldav url is: |
I found the cause for my error #404. In line 299 the |
maybe you could also use the content of the |
i would also love support for google ;-) |
@white-gecko i'm getting error 405 ... how did you solve this ? removing the .vcf ending didn't work for me.. using the german url and removing .vcf just hangs... |
Regarding to wikipedia error 405 is method not allowed, meaning something with GET/POST/… is wrong. My diff for
And I retrieve the contact data with following script:
|
I bumped into this issue as well... I don't think Google is doing anything wrong with their CardDAV setup, but it is certainly different to the other CardDAV servers I've been trying. According to RFC 6352 (http://tools.ietf.org/html/rfc6352), "File names for vCards are commonly suffixed by ".vcf", and clients may choose to use the same convention for URLs." so .vcf is somewhat unclearly defined in that the RFC implies that both with and without the extension is acceptable. I've committed what I hope is a good fix for the issue - essentially I've added the ability to set the extension to be used for the vcard queries, as well as a check to set_url that automatically configures it correctly when using Google. See: |
Hello I think google URL has been changed to
|
Hi @mrahmadt, |
Hi,
Have you been able to connect to google?
http://support.google.com/mail/bin/answer.py?hl=en&answer=2753077
tried
$carddav = new carddav_backend('https://google.com/');
$carddav->enable_debug();
$carddav->set_auth('[email protected]', 'password');
but fails.
The text was updated successfully, but these errors were encountered: