[Melbourne-pm] (paid) Assistance required for Google calendar hack

Nathan Bailey Nathan.Bailey at its.monash.edu
Tue Aug 18 15:16:34 PDT 2009

I ended up trying WCAP code after 20-odd variations of:
< test.ics lwp-request -xuSe -C username at gmail.com:password -c 'text/ 
calendar' -m PUT https://www.google.com/calendar/dav/username%40gmail.com/events
failed with a 401. My code also failed with a 401 (lacking basic auth)  
which is what lead to trying WCAP authentication (that and tiredness I  
guess :-)

After a bit more playing around I'm now getting my .ics file from  
Google with CalDAV, but it turns out that Google doesn't support  
MKCALENDAR, the create method, and there doesn't appear to be a DELETE- 
type method in CalDAV (it's possible that the HTTP DAV one works but I  
haven't found anything that says it would).

So now I need to decide if I follow the original path, or put on my  
lazy (Toby) gloves (Alfie) and subscribe to an ics file published on  
another server (Stephen) :-)

thanks everyone for the help!

On 18/08/2009, at 9:56 AM, Daniel Pittman wrote:

> Nathan Bailey <Nathan.Bailey at its.monash.edu> writes:
>> If this worked, it would be the ideal simple solution, but I can't  
>> get it to
>> work (even with the "right" URL, according to
>> http://code.google.com/apis/calendar/developers_guide_caldav.html) .
> ...um:
>    To use the CalDAV interface, a client program initially connects  
> with the
>    calendar server at one of two starting points. In either case, the
>    connection must be made over HTTPS, and Basic authentication  
> should be
>    provided for the user's Google account, consisting of the full  
> email
>    address and password.
> [...]
>> my $CALSERVER = 'https://www.google.com/calendar/dav/username@gmail.com/user' 
>> ;
>> my $user = 'username at gmail.com';
>> my $pass = 'password';
>> my $content = wcap_command("login", "user=$user", "password=$pass");
> This has nothing to do with HTTP Basic authentication.  Try sending  
> the
> content via PUT with the username and password via HTTP Basic  
> authentication
> and the 401 (you didn't supply HTTP basic authentication details)  
> error will
> go away.
> Um, what gave you the idea that the wcap command thing was right?
> The Google pages don't mention it, no one here mentioned it as far  
> as I can
> tell, so why on earth did you try using wcap rather than following the
> instructions as Google have written them?
> Regards,
>        Daniel
> -- 
> ✣ Daniel Pittman            ✉ daniel at rimspace.net> +61 401 155 707
>               ♽ made with 100 percent post-consumer electrons
>   Looking for work?  Love Perl?  In Melbourne, Australia?  We are  
> hiring.
> _______________________________________________
> Melbourne-pm mailing list
> Melbourne-pm at pm.org
> http://mail.pm.org/mailman/listinfo/melbourne-pm

More information about the Melbourne-pm mailing list