I'm trying to write a caldav client, and I can't seem to get authorization working.
In order to understand the protocol, I've written a little customized proxy to go between ical.app and google calendar and capture what gets sent back and forth between the two. I capture the request from ical, forward it to google calendar over an https connection and then send the response back to ical.app. The first request is a PROPFIND for my calendar, (with the path calendar/dav/[email protected]/user) and the response comes back as a 302 redirect to http://www.google.com I reckoned that this was really an unauthorized response in disguise. The original request from ical.app didn't contain an authorization header. At first I thought that ical.app wouldn't send it to my proxy over a non-ssl connection, but when I set the proxy up with an ssl connection, there was still no authorization header, and the result was a same, a redirect to www.google.com So I then had the proxy force the addition of a basic authorization header: Authorization Basic xxxxxxx where xxxxxx is the Base64 encoding of my "[email protected]:pppp" where pppp is my valid password. I STILL get the redirect to www.google.com. What am I missing? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
