<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="-1"><font face="Helvetica, Arial, sans-serif">That
works indeed and I'll switch over to sync-collection +
multiget</font></font> as well, but [Google's]
<calendar-data>'s behavior in response to
<sync-collection> is quite a nut in its own right. Delete
the last instance you have of a repeating event without a master
and Google gets you a "200 OK" with an empty VCALENDAR. Go GET or
multiget it and you get 404.<br>
</p>
<p>I haven't checked other servers. Happen to know how Cyrus
behaves?</p>
<p><br>
</p>
<p>
<blockquote type="cite">Surely <caldav:calendar-data> isn't
defined differently in the REPORT context and in the PROPFIND
context?</blockquote>
</p>
<p>Correction to my own question --- "defined differently in
<sync-collection> vs <calendar-multiget>". Noticed in
RFC 4791 that <calendar-data> isn't supposed to be returned
in PROPFIND.<br>
</p>
<br>
<div class="moz-cite-prefix">On 06/01/2018 09:28 PM, Bron Gondwana
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1527888528.2298522.1393533272.628B5A57@webmail.messagingengine.com">
<title></title>
<style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
<div style="font-family:Arial;">What happens if you just fetch the
href in changes and then use a get or multiget to fetch the
calendar data?<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">I'm pretty sure I changed all our
perl client code to do that a while back for unrelated reasons
(ok, because some servers just error out if you try to fetch too
many items at once, so we batch the calendar data requests).</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">Bron.</div>
<div><br>
</div>
<div><br>
</div>
<div>On Sat, Jun 2, 2018, at 02:58, Andri Möll wrote:<br>
</div>
<blockquote type="cite">
<p><span class="size" style="font-size:small"><span class="font"
style="font-family:Helvetica, " Arial", "
sans-serif"">Hey,</span></span><br>
</p>
<p><span class="size" style="font-size:small"><span class="font"
style="font-family:Helvetica, " Arial", "
sans-serif"">Does anyone know what's up with Google
Calendar's CalDAV REPORT <sync-collection> with
<sync-token> response only returning updated
recurring event instances in <caldav:calendar-data>
and not the entire iCalendar with its master and other
[unchanged] instances?</span></span> Surely
<caldav:calendar-data> isn't defined differently in the
REPORT context and in the PROPFIND context?<br>
</p>
<p>Throwing in <caldav:comp> in hopes that it'll trigger a
full response doesn't seem to work either.<br>
</p>
<p><br>
</p>
<blockquote type="cite">
<div style="font-family:Arial;"><caldav:calendar-data><br>
</div>
<div style="font-family:Arial;"> <caldav:comp
name="VCALENDAR"><br>
</div>
<div style="font-family:Arial;"> <caldav:allprop/><br>
</div>
<div style="font-family:Arial;"> <caldav:allcomp/><br>
</div>
<div style="font-family:Arial;"> </caldav:comp><br>
</div>
<div style="font-family:Arial;"> </caldav:calendar-data><br>
</div>
</blockquote>
<div style="font-family:Arial;"><br>
</div>
<p><br>
</p>
<p>Thanks!<br>
</p>
<p>Andri<br>
</p>
<div><u>_______________________________________________</u><br>
</div>
<div>caldeveloper-l mailing list<br>
</div>
<div><a href="mailto:caldeveloper-l@lists.calconnect.org"
moz-do-not-send="true">caldeveloper-l@lists.calconnect.org</a><br>
</div>
<div><a
href="http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org"
moz-do-not-send="true">http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org</a><br>
</div>
</blockquote>
<div style="font-family:Arial;"><br>
</div>
<div id="sig56629417">
<div class="signature">--<br>
</div>
<div class="signature"> Bron Gondwana, CEO, FastMail Pty Ltd<br>
</div>
<div class="signature"> <a class="moz-txt-link-abbreviated" href="mailto:brong@fastmailteam.com">brong@fastmailteam.com</a><br>
</div>
<div class="signature"><br>
</div>
</div>
</blockquote>
<br>
</body>
</html>