<div dir="ltr">Thanks very much for this --- you'll have to bear with me as this it involves more detailed knowledge of the protocol than I have handy, and I'll have to check up with people.<div><br></div><div>One word of warning: the 'Import ICS' feature in our UI does <i>not</i> behave the same way as the API --- it makes a copy of the event and adds it to the user's calendar, which means the organiser gets changed. I don't think it's relevant in this case but I'd strongly recommend testing with CalDAV instead.</div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, 6 Jun 2018 at 23:52 Arnaud Quillaud <<a href="mailto:arnaudq@quillaud.org">arnaudq@quillaud.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="m_-2664024233408842978moz-cite-prefix">On 01/06/2018 23:28, Bron Gondwana
      wrote:<br>
    </div>
    <blockquote type="cite">
      
      
      <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>
    </blockquote></div><div bgcolor="#FFFFFF" text="#000000">
    There is a more fundamental reason to always use a CalDAV multi-get
    REPORT: caldav:calendar-data is not a WebDAV property and can be
    used *only* in the context of a CalDAV REPORT. From
    <a class="m_-2664024233408842978moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc4791#section-9.6" target="_blank">https://tools.ietf.org/html/rfc4791#section-9.6</a><br>
    <br>
    <blockquote>
      <pre class="m_-2664024233408842978newpage" style="font-size:13.333333015441895px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration:none">Note:  The CALDAV:calendar-data XML element is specified in requests
      and responses inside the DAV:prop XML element as if it were a
      WebDAV property.  However, the CALDAV:calendar-data XML element is
      not a WebDAV property and, as such, is not returned in PROPFIND
      responses, nor used in PROPPATCH requests.</pre>
    </blockquote>
    <br>
    In practice of course, most servers will return "something" when
    calendar-data is asked for in a generic WebDAV REPORT or in a
    PROPFIND request. That "something" seems to be not so well defined
    in the case of Google.<br>
    <br>
    Arnaud Q</div><div bgcolor="#FFFFFF" text="#000000"><br>
    <blockquote type="cite">
      <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="m_-2664024233408842978size" style="font-size:small"><span class="m_-2664024233408842978font">Hey,</span></span><br>
        </p>
        <p><span class="m_-2664024233408842978size" style="font-size:small"><span class="m_-2664024233408842978font">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" target="_blank">caldeveloper-l@lists.calconnect.org</a><br>
        </div>
        <div><a href="http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org" target="_blank">http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org</a><br>
        </div>
      </blockquote>
      <div style="font-family:Arial"><br>
      </div>
      <div id="m_-2664024233408842978sig56629417">
        <div class="m_-2664024233408842978signature">--<br>
        </div>
        <div class="m_-2664024233408842978signature">  Bron Gondwana, CEO, FastMail Pty Ltd<br>
        </div>
        <div class="m_-2664024233408842978signature">  <a class="m_-2664024233408842978moz-txt-link-abbreviated" href="mailto:brong@fastmailteam.com" target="_blank">brong@fastmailteam.com</a><br>
        </div>
        <div class="m_-2664024233408842978signature"><br>
        </div>
      </div>
      <br>
      <fieldset class="m_-2664024233408842978mimeAttachmentHeader"></fieldset>
      <br>
      <pre>_______________________________________________
caldeveloper-l mailing list
<a class="m_-2664024233408842978moz-txt-link-abbreviated" href="mailto:caldeveloper-l@lists.calconnect.org" target="_blank">caldeveloper-l@lists.calconnect.org</a>
<a class="m_-2664024233408842978moz-txt-link-freetext" href="http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org" target="_blank">http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org</a>
</pre>
    </blockquote>
    <br>
  </div>

_______________________________________________<br>
caldeveloper-l mailing list<br>
<a href="mailto:caldeveloper-l@lists.calconnect.org" target="_blank">caldeveloper-l@lists.calconnect.org</a><br>
<a href="http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org" rel="noreferrer" target="_blank">http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org</a><br>
</blockquote></div>