February 2011 - calendarserver-dev - lists.macosforge.org

[Calendar and Contacts Server] #391: 'run' script installs Twisted plugins to wrong location on x86_64 systems
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#391: 'run' script installs Twisted plugins to wrong location on x86_64 systems ---------------------------------+------------------------------------------ Reporter: s.adam@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | ---------------------------------+------------------------------------------ I may have made a beginner's mistake as this is the first time I deal with Twisted, but I believe that CalendarServer installs the Twisted plugins to the wrong location on x86_64 systems. CalendarServer will create a both '/usr/lib/python2.X/site-packages' (sitelib) and '/usr/lib64/python2.X/site-packages' (sitearch) directory and places the Twisted files in sitearch directory and the Twisted plugins in the sitelib. Attempting to start the server will have Twisted search only the sitearch directory and produce an error since the caldav plugin isn't known. I am using Fedora 13 x86_64 which has Python 2.6. -- Ticket URL: <http://trac.calendarserver.org/ticket/391> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #389: Allow 400 (Bad Request) for bad requests
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#389: Allow 400 (Bad Request) for bad requests ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Task | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- Validator prepostcondition only allows 403, 409, 507 as a status even though 400 seems valid and sometimes more appropriate (e..g non-UTC datetime in time-range): DAV says {{{ Servers MAY reject questionable requests (even though they consist of well-formed XML), for instance, with a 400 (Bad Request) status code and an optional response body explaining the problem. }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/389> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #387: Content-type could use its own verifier
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#387: Content-type could use its own verifier ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- Tests fail because the content-type header value doesn't match but is actually valid, e.g. g test for {{{ text/calendar;charset=utf-8 }}} and receive {{{ text/calendar; charset=UTF-8 }}} The space(s) after the semi-colon are valid as is the UC "UTF-8" This might be complicated enough to justify its own verifier -- Ticket URL: <http://trac.calendarserver.org/ticket/387> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #386: DTSTAMP should be (partially) filtered in calendarDataMatch
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#386: DTSTAMP should be (partially) filtered in calendarDataMatch ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- DTSTAMP is equivalent to LAST-MODIFIED for entities without a METHOD so should be filtered for those tests. For example, tests in put.xml fail because the DTSTAMP value changes, DTSTAMP from rfc5545: {{{ Purpose: In the case of an iCalendar object that specifies a "METHOD" property, this property specifies the date and time that the instance of the iCalendar object was created. In the case of an iCalendar object that doesn't specify a "METHOD" property, this property specifies the date and time that the information associated with the calendar component was last revised in the calendar store. ... In the case of an iCalendar object that specifies a "METHOD" property, this property differs from the "CREATED" and "LAST- MODIFIED" properties. These two properties are used to specify when the particular calendar data in the calendar store was created and last modified. This is different than when the iCalendar object representation of the calendar service information was created or last modified. In the case of an iCalendar object that doesn't specify a "METHOD" property, this property is equivalent to the "LAST-MODIFIED" property. }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/386> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #385: This is not working properly
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#385: This is not working properly --------------------------------+------------------------------------------- Reporter: jpr.guru@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 4: Nice to have | Milestone: Later Component: Calendar Server | Severity: Performance Keywords: performance | --------------------------------+------------------------------------------- This application is not working properly on my browser IE 8 -- Ticket URL: <http://trac.calendarserver.org/ticket/385> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #383: something missing :
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#383: something missing : ------------------------------+--------------------------------------------- Reporter: jduffas1@… | Owner: wsanchez@… Type: Enhancement | Status: new Priority: 4: Nice to have | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | ------------------------------+--------------------------------------------- hello, we should have the choice, as in zimbra : -Allow both internal and external users to see my free/busy information -Allow only local users to see my free/busy information -Don't let anyone see my free/busy information -Allow only the following local users to see my free/busy information :... and : -Allow both internal and external users to invite me to meetings -Allow only local users to invite me to meetings -Don't let anyone to invite me to meetings -Allow only the following local users to invite me to meetings:... -- Ticket URL: <http://trac.calendarserver.org/ticket/383> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #376: Lightning with wrong crendentals saved crashes calendarserver
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#376: Lightning with wrong crendentals saved crashes calendarserver -------------------------------+-------------------------------------------- Reporter: rahul@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.5 Component: Calendar Server | Severity: Crash/data loss Keywords: | -------------------------------+-------------------------------------------- Steps to reproduce: 1. Setup Calendarserver (I installed Calendarserver 2.4 on Debian Lenny)[[BR]] 2. Install Thunderbird with Lightning plugin[[BR]] 3. Add the caldav url to lightninig[[BR]] 4. Upon prompting for password, enter wrong credentials, check "Use Password Manager to remember this password" and click on OK.[[BR]] Now monitor the server. Authentication requests are sent continuously and the calendar server CPU usage goes very high. While I understand that this is primarily a bug in Lightning, it is also a problem with Calendarserver because it is susceptible to DOS attacks. I believe the developers are aware of this issue. If not, kindly take this into consideration for the next major release. -- Ticket URL: <http://trac.calendarserver.org/ticket/376> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[CalendarServer] #353: 'Calendar data does not conform to CalDAV requirements: METHOD property is not allowed in CalDAV iCalendar data'
by CalendarServer 09 Sep '11

09 Sep '11

#353: 'Calendar data does not conform to CalDAV requirements: METHOD property is not allowed in CalDAV iCalendar data' -----------------------------+---------------------------------------------- Reporter: alex@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 3: Important | Milestone: Component: Calendar Server | Severity: Serious Keywords: | -----------------------------+---------------------------------------------- This is what I get when trying to publish from ical or sunbird from different machines. I use 1.2.dfsg-8 on debian stable -- Ticket URL: <http://trac.calendarserver.org/ticket/353> CalendarServer </> HTTP/WebDAV/CalDAV Server

2 11

[CalendarServer] #330: group as no calendar home
by CalendarServer 03 Aug '11

03 Aug '11

#330: group as no calendar home ------------------------------+--------------------------------------------- Reporter: jduffas1@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Serious Keywords: | ------------------------------+--------------------------------------------- I upgraded to the latest version, and all my groups are broken. iCal says that there is no home calendar for group, and when I look in the server terminal, it says : 2009-03-30 17:18:22+0200 [-] [caldav-8009] [PooledMemCacheProtocol,client] [twistedcaldav.static#info] Directory record <XMLDirectoryRecord[groups@21927289-115a-5605-8596-cd1b708d3750(icalconsult Realm)] F2F2B56A-7B0E-498C-816F-1DA30D8A4167(nous_deux) 'nous deux'> is not enabled for calendaring I use the accounts.xml file. -- Ticket URL: <http://trac.calendarserver.org/ticket/330> CalendarServer </> HTTP/WebDAV/CalDAV Server

4 30

[Calendar and Contacts Server] #371: better parsing of returned properties would help
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#371: better parsing of returned properties would help ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- Tests fail with messages like: {{{ Failed Verifier: propfindItems Items not returned in report (OK) for /ucaldav/user/user01/Inbox/: ('urn:ietf:params:xml:ns:caldavschedule-default-calendar-URL', '<href xmlns="DAV:">/ucaldav/user/user01/calendar</href>') Unexpected items returned in report (OK) for /ucaldav/user/user01/Inbox/: (u'urn:ietf:params:xml:ns:caldavschedule- default-calendar-URL', u'<href>/ucaldav/user/user01/calendar/</href>') }}} because of unexpected formats to the response, e.g. {{{ <?xml version="1.0" encoding="UTF-8" ?> <multistatus xmlns="DAV:" xmlns:ns1="urn:ietf:params:xml:ns:caldav" xmlns:ns2="http://www.w3.org/2002/12/cal/ical#"> <response> <href>/ucaldav/user/user01/Inbox/</href> <propstat> <prop> <ns1:schedule-default-calendar-URL> <href>/ucaldav/user/user01/calendar/</href> </ns1:schedule-default-calendar-URL> </prop> <status>HTTP/1.1 200 ok</status> </propstat> </response> </multistatus> }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/371> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3