[CalendarServer-users] Connection aborted - took too long to close

[Cyrus Daboo]

Can you login directly on the server and run the curl command?

-- 
Cyrus Daboo
(Tapped out on my iPhone)


> On Feb 15, 2015, at 11:15 AM, Jacques Distler <distler at golem.ph.utexas.edu> wrote:
> 
> 
>> On Feb 15, 2015, at 9:15 AM, Cyrus Daboo <cdaboo at apple.com> wrote:
>> 
>> Hi Jacques,
>> 
>> --On February 14, 2015 at 2:19:58 PM -0600 Jacques Distler <distler at golem.ph.utexas.edu> wrote:
>> 
>>> 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.
>> 
>> First off I cannot guarantee that Range requests work correctly (and it does appear from your analysis they may not be). However, no CalDAV client should need to do that as they should be fetching small resources.
> 
> Evidently, they do sometimes fetch larger resources, as Calendar.app on MacOSX and iOS exhibit the same problem with the same user's calendar.
> 
>> The test you are doing - a GET on a calendar collection - is not something CalDAV clients would do. That said, a GET without range should work fine - but it appears your browser is using range.
> 
> Sorry. I didn't explain that properly.
> 
> The browser's FIRST request is an ordinary GET (without a range). The Server sends a 200 response, but closes the connection after sending 62K of data. The browser's SUBSEQUENT requests are Range Requests. Each time, the server sends a 206 Response, promising the REST of the resource, but each time it closes the connection after sending 62K of data.
> 
> I have to clear the browser's cache (which I can do) to get it to return to making an ordinary GET request (without a range).
> 
>> To avoid that pull up a terminal and use the "curl" command line tool to fetch the data, e.g.:
>> 
>> curl https://golem.ph.utexas.edu:8443/calendars/users/YYYYY/calendar/
>> 
>> Try that and see whether you get time outs.
> 
> Yes. I do.
> 
> Here are the headers returned when I use "curl -D -":
> 
> HTTP/1.1 200 OK
> Content-Type: text/html;charset=utf-8
> Date: Sun, 15 Feb 2015 16:06:50 GMT
> ETag: "81366bb1ab22b568dec1c1d79b156510"
> Strict-Transport-Security: max-age=604800
> Server: Twisted/12.3.0 TwistedWeb/9.0.0
> DAV: 1, access-control, calendar-access, calendar-schedule, calendar-auto-schedule, calendar-availability, inbox-availability, calendar-proxy, calendars
> erver-private-events, calendarserver-private-comments, calendarserver-sharing, calendarserver-sharing-no-scheduling, calendar-query-extended, calendar-d
> efault-alarms, calendar-managed-attachments, calendarserver-partstat-changes, calendar-no-timezone, calendarserver-recurrence-split, addressbook, extend
> ed-mkcol, calendarserver-principal-property-search, calendarserver-principal-search, calendarserver-home-sync
> Accept-Ranges: bytes
> Content-Length: 509580
> Last-Modified: Sun, 15 Feb 2015 04:36:45 GMT
> Connection: close
> 
> But, despite promising 497.6K of data in the header, the server returns 62K and closes the connection.
> 
> JD