> On Feb 14, 2015, at 1:51 PM, Jacques Distler <dist...@golem.ph.utexas.edu> > wrote: > > HTTP/1.1 206 Partial Content > Server: Twisted/12.3.0 TwistedWeb/9.0.0 > Content-Length: 318794 > Content-Range: bytes 190464-509257/509258 > Etag: "8594b290ec42129aea36d880441319bf" > Date: Sat, 14 Feb 2015 19:42:43 GMT > Last-Modified: Fri, 13 Feb 2015 21:17:20 GMT > DAV: 1, access-control, calendar-access, calendar-schedule, > calendar-auto-schedule, calendar-availability, inbox-availability, > calendar-proxy, calendarserver-private-events, > calendarserver-private-comments, calendarserver-sharing, > calendarserver-sharing-no-scheduling, calendar-query-extended, > calendar-default-alarms, calendar-managed-attachments, > calendarserver-partstat-changes, calendar-no-timezone, > calendarserver-recurrence-split, addressbook, extended-mkcol, > calendarserver-principal-property-search, calendarserver-principal-search, > calendarserver-home-sync > Strict-Transport-Security: max-age=604800 > Accept-Ranges: bytes > Content-Type: text/html;charset=utf-8 > Connection: close > ---------------------------------------------------------- > > Note that the requested byte range has changed --- as if the client got bytes > 126976-190463 in the previous response.
And, indeed, that pattern continues. When I try again, the client requests "Range: bytes=253952-". Each time, the Server sends precisely 63488 bytes (62 kB) of data, before prematurely closing the connection.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-users
