From: Jason Riedy <jason@lovesgoodfood.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-caldav for Google or Zimbra?
Date: Thu, 26 Sep 2013 09:51:49 -0400 [thread overview]
Message-ID: <87pprvr8qy.fsf@qNaN.sparse.dyndns.org> (raw)
In-Reply-To: 87r4ccrp9s.fsf@ucl.ac.uk
And Eric S. Fraga writes:
> Can you expand on this? I am not sure what you mean by
> endpoint. I use org-caldav-sync several times a day and it
> generally works very well with Google's calendar service.
Google has deprecated the URL in org-caldav, and that old URL
does not work for me. The new one is documented at
https://developers.google.com/google-apps/calendar/caldav/v2/guide#new_endpoint
Fiddling with the regexp in org-caldav-events-url triggers an
error apparently in the authentication code:
> Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
> url-http-handle-authentication(nil)
> url-http-parse-headers()
> url-http-chunked-encoding-after-change-function(415 440 25)
> url-http-wait-for-headers-change-function(1 453 452)
> url-http-generic-filter(#<process apidata.googleusercontent.com> "HTTP/1.1 401 Unauthorized\nWWW-Authenticate: Bearer realm=\"https://www.google.com/accounts/AuthSubRequest\"\nContent-Type: text/html; charset=UTF-8\nDate: Thu, 26 Sep 2013 13:48:37 GMT\nExpires: Thu, 26 Sep 2013 13:48:37 GMT\nCache-Control: private, max-age=0\nX-Content-Type-Options: nosniff\nX-Frame-Options: SAMEORIGIN\nX-XSS-Protection: 1; mode=block\nServer: GSE\nAlternate-Protocol: 443:quic\nTransfer-Encoding: chunked\n\ne\nLogin Required\n0\n\n")
> accept-process-output(#<process apidata.googleusercontent.com>)
> #[0 "\302\303\300@!)\207" [(#<process apidata.googleusercontent.com>) inhibit-quit nil accept-process-output] 2 "\n\n(fn)"]()
> funcall(#[0 "\302\303\300@!)\207" [(#<process apidata.googleusercontent.com>) inhibit-quit nil accept-process-output] 2 "\n\n(fn)"])
> url-retrieve-synchronously("https://apidata.googleusercontent.com/caldav/v2/jason.riedy/events/")
> url-http-options("https://apidata.googleusercontent.com/caldav/v2/jason.riedy/events/")
> url-dav-supported-p("https://apidata.googleusercontent.com/caldav/v2/jason.riedy/events/")
> (if (url-dav-supported-p (org-caldav-events-url)) nil (error "The URL %s does not seem to accept DAV requests" (org-caldav-events-url)))
> org-caldav-sync()
> eval((org-caldav-sync) nil)
> eval-last-sexp-1(nil)
> eval-last-sexp(nil)
> call-interactively(eval-last-sexp nil nil)
Someone on github reported the same issue.
--
Jason
next prev parent reply other threads:[~2013-09-26 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 21:27 org-caldav for Google or Zimbra? Jason Riedy
2013-09-26 7:54 ` Eric S Fraga
2013-09-26 13:51 ` Jason Riedy [this message]
2013-09-26 18:05 ` David Engster
2013-09-26 19:00 ` Jason Riedy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pprvr8qy.fsf@qNaN.sparse.dyndns.org \
--to=jason@lovesgoodfood.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).