Calendar:GDATA Provider: Difference between revisions

Jump to navigation Jump to search
Line 25: Line 25:
# Click on either of the two XML buttons shown at the bottom.
# Click on either of the two XML buttons shown at the bottom.


Authentication is always done securely via https. If you would also like to securely transfer your calendar data, then just change the URL to https://.. instead of http://...
Authentication is always done securely via https, your password is not sent cleartext. However, an Authentication Token is sent with each request that can be used to further manipulate your calendar. '''To ensure full privacy, be sure to change the URL from http://.. to https://...'''


Note that the provider does not directly use your private url. The Calendar is still accessible when you [http://www.google.com/support/calendar/bin/answer.py?answer=34576 reset your private url].
Note that the provider does not directly use your private url. The Calendar is still accessible when you [http://www.google.com/support/calendar/bin/answer.py?answer=34576 reset your private url].
258

edits

Navigation menu