f5f88c61aa
When finding a new URL, we must be prepared to reinitialize the Neon session with the new host settings. To implement this, candidates are now full URIs, not just paths on the initial host. A home set on iCloud contains full URLs, not just paths. We need to parse the individual entries, which happens to work for paths and URLs because paths are just special URLS without an explicit host. iCloud does not have .well-known support on its www.icloud.com server. To support lookup with a non-icloudd.com email address, we must do DNS SRV lookup when access to .well-known URLs fails. We do this without a www prefix on the host first, because that is what happens to work for icloud.com. With these changes it becomes possible to do database scans on Apple iCloud, using syncURL=https://www.icloud.com or syncURL=https://icloud.com. The former is a bit faster because the icloud.com redirects to www.icloud.com before we end up doing the DNS SRV lookup to find the CalDAV resp. CardDAV hosts.
19 lines
1.4 KiB
Plaintext
19 lines
1.4 KiB
Plaintext
Google Calendar APIs Terms of Service
|
|
Last modified: April 20, 2012
|
|
|
|
By using this API, you consent to be bound by these terms in addition to the Google APIs Terms of Service ("API ToS") at http://code.google.com/apis/terms/index.html.
|
|
|
|
1. Data location
|
|
1. You acknowledge that any information provided by users through the Calendar APIs will be handled and stored by Google and that such information may be stored and processed in the United States or any other country in which Google or its subsidiaries or affiliated legal entities maintain facilities.
|
|
2. By using the Calendar APIs, you consent and will obtain any necessary consent from your users to any such transfer of information.
|
|
|
|
2. Deprecation Policy
|
|
Google will announce if we intend to discontinue or make backwards incompatible changes to this API or Service. We will use commercially reasonable efforts to continue to operate Versions 1 and 2 of the Calendar Data API without these changes until November 17, 2014, unless (as Google determines in its reasonable good faith judgment):
|
|
|
|
* required by law or third party relationship (including if there is a change in applicable law or relationship), or
|
|
* doing so could create a security risk or substantial economic or material technical burden.
|
|
|
|
This Deprecation Policy doesn't apply to versions, features, and functionality labeled as "experimental."
|
|
|
|
After November 17, 2014, this Deprecation Policy will not apply.
|