May 2008 - calendarserver-dev - lists.macosforge.org

[CalendarServer] #277: Set process name
by CalendarServer 26 Oct '09

26 Oct '09

#277: Set process name --------------------------------+------------------------------------------- Reporter: wsanchez(a)apple.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 3: Important | Milestone: 2.x Component: Calendar Server | Version: Severity: Other | Keywords: --------------------------------+------------------------------------------- Server should do `setproctitle` or whatever to set the process name so that it isn't `python`, which makes it harder to distinguish from other python programs. I think this would require a C extension, since Python doesn't provide API for it. -- Ticket URL: <https://trac.calendarserver.org/ticket/277> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] #274: caldavd does not properly quote parameters
by CalendarServer 26 Oct '09

26 Oct '09

#274: caldavd does not properly quote parameters ---------------------------------+------------------------------------------ Reporter: kmdurbrow(a)gmail.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Version: Severity: Other | Keywords: ---------------------------------+------------------------------------------ Last line of caldavd {{{ ${configfile} }}} should be quoted -- Ticket URL: <https://trac.calendarserver.org/ticket/274> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] #276: Virtual hostname not found (no apple-serviceinfo LDAP attribute)
by CalendarServer 18 Jul '08

18 Jul '08

#276: Virtual hostname not found (no apple-serviceinfo LDAP attribute) -----------------------------------------+---------------------------------- Reporter: dnicolson(a)pixelgroup.com.au | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Version: Severity: Other | Keywords: -----------------------------------------+---------------------------------- After some difficulty setting up CalendarServer on OS X Server 10.4 (svn, python, ez_install failing at different places), I am able to connect from iCal using the XML credentials. I'm experiencing a problem using OpenDirectory as the connection method. The error is: twistedcaldav.directory.appleopendirectory.OpenDirectoryInitError: Open Directory (node=/Search) has no /Computers records with a virtual hostname: <hostname> Running this command I am able to see the hostname of the machine: $ dscl /Search list /Computers I am also able to see the LDAP attributes when running this command: $ dscl /Search read /Computers/<hostname> Looking at the LDAP log (/var/log/slapd.log), I can see this: get_ssa: conn 4758 unknown attribute type=apple-serviceinfo (17) After Googling this, people had problems with iCal Server under Leopard and created the apple-serviceinfo attribute. I attempted this using: $ sudo dscl /LDAPv3/127.0.0.1 -create Computers/pixelfs dsAttrTypeNative :apple-serviceinfo "" And I received this error: <main> attribute status: eDSPermissionError Any thoughts welcome. -- Ticket URL: <https://trac.calendarserver.org/ticket/276> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 3

[CalendarServer] #278: group and invitation
by CalendarServer 28 May '08

28 May '08

#278: group and invitation ------------------------------+--------------------------------------------- Reporter: jduffas1(a)free.fr | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 2: Expected | Milestone: Component: Calendar Server | Version: trunk Severity: Serious | Keywords: group invitation invite ------------------------------+--------------------------------------------- When someone in a group whant to invite someone out of the group, it bugs... details : I make an event, click on "invite" enter an email adress, confirm, then the whell turns without ending in front of the group calendar... even if I delete the event, it turns... event if I restart the server and ical, it keeps turning. the solution is that every peoples of the group erase the event (I juste had a try with a 2 peoples group), then it stop turning, and it' s usable again. -- Ticket URL: <https://trac.calendarserver.org/ticket/278> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 1

CalDAVClientLibrary browser patch
by Frank Strauß 28 May '08

28 May '08

I was wondering why I could not type a "b" to the command line. :-) I am not really familiar with readline, but maybe this is what we want. Index: src/browser/baseshell.py =================================================================== --- src/browser/baseshell.py (revision 2509) +++ src/browser/baseshell.py (working copy) @@ -62,7 +62,7 @@ map(readline.add_history, self.history) readline.set_completer(self.complete) - readline.parse_and_bind("bind ^I rl_complete") + readline.parse_and_bind("tab: complete") while True: cmdline = raw_input("%s > " % (self.prefix,))

2 1

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP
by CalendarServer 27 May '08

27 May '08

#260: OpenLDAP ---------------------------------------+------------------------------------ Reporter: jusiskin(a)franticfilms.com | Owner: wsanchez(a)apple.com Type: Feature | Status: new Priority: 3: Important | Milestone: 2.x Component: Calendar Server | Version: Severity: Other | Resolution: Keywords: | ---------------------------------------+------------------------------------ Comment (by wsanchez(a)apple.com) The module needs to implement the `IDirectoryService` API (see source:CalendarServer/trunk/twistedcaldav/directory/idirectory.py). The XML directory service is a pretty simple example: (source:CalendarServer/trunk/twistedcaldav/directory/xmlfile.py) The OpenDirectory service is considerably more complicates, in large part due to a complicated schema that we implemented and now hope to get rid of: (source:CalendarServer/trunk/twistedcaldav/directory/appleopendirectory.py) I haven't seen any work started on this yet, so I don't know of a module that starts this work from which you can pick up, so I think you have to start from scratch. -- Ticket URL: <https://trac.calendarserver.org/ticket/260#comment:4> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP
by CalendarServer 26 May '08

26 May '08

#260: OpenLDAP ---------------------------------------+------------------------------------ Reporter: jusiskin(a)franticfilms.com | Owner: wsanchez(a)apple.com Type: Feature | Status: new Priority: 3: Important | Milestone: 2.x Component: Calendar Server | Version: Severity: Other | Resolution: Keywords: | ---------------------------------------+------------------------------------ Comment (by register(a)greatwallsys.com) I might be interested in contributing some effort to this. Simple authentication over SSL/TLS would be acceptable to me (although OpenLDAP will support anything that Cyrus SASL supports, which does include DIGEST.) What other work needs to be done in order to support OpenLDAP? Would it be possible to generalize the schema requirements at all, say by allowing mapped attribute types and user-defined search filters? -- Ticket URL: <https://trac.calendarserver.org/ticket/260#comment:3> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

[CalendarServer] #275: Please merge the more-kerberos branch into trunk
by CalendarServer 23 May '08

23 May '08

#275: Please merge the more-kerberos branch into trunk -----------------------------+---------------------------------------------- Reporter: agx(a)sigxcpu.org | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: PyKerberos | Version: Severity: Other | Keywords: -----------------------------+---------------------------------------------- Hi, we currently have to branches in pykerberos: trunk (with pw changing support) and more-kerberos with basic wrap/unwarp support (enough to to handle imaps, the API is extendable). Can these please be merged since tracking both seems more work then necessary. -- Guido -- Ticket URL: <https://trac.calendarserver.org/ticket/275> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 4

Re: [CalendarServer] #273: `valid-calendar-object-resource` precondition failure returns with a `403 FORBIDDEN`, should be `412 PRECONDITION FAILED`
by CalendarServer 08 May '08

08 May '08

#273: `valid-calendar-object-resource` precondition failure returns with a `403 FORBIDDEN`, should be `412 PRECONDITION FAILED` --------------------------------+------------------------------------------- Reporter: wsanchez(a)apple.com | Owner: cdaboo(a)apple.com Type: Defect | Status: closed Priority: 3: Important | Milestone: 1.x Component: Calendar Server | Version: Severity: Other | Resolution: worksforme Keywords: | --------------------------------+------------------------------------------- Comment (by cdaboo(a)apple.com) And was that 403 error the result of a failure caused by the conditional headers? If the conditional header test failed, then it should have been a 412. If the conditional header test passed, but something else failed, then 403 is appropriate. -- Ticket URL: <https://trac.calendarserver.org/ticket/273#comment:7> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer] #273: `valid-calendar-object-resource` precondition failure returns with a `403 FORBIDDEN`, should be `412 PRECONDITION FAILED`
by CalendarServer 08 May '08

08 May '08

#273: `valid-calendar-object-resource` precondition failure returns with a `403 FORBIDDEN`, should be `412 PRECONDITION FAILED` --------------------------------+------------------------------------------- Reporter: wsanchez(a)apple.com | Owner: cdaboo(a)apple.com Type: Defect | Status: closed Priority: 3: Important | Milestone: 1.x Component: Calendar Server | Version: Severity: Other | Resolution: worksforme Keywords: | --------------------------------+------------------------------------------- Comment (by mail(a)david-reid.com) Replying to [comment:5 cdaboo(a)apple.com] > Section 12.1 defines how the 412 code should be used. Note that it says 412 MUST NOT be returned when there are no conditional headers present. > > Section 16 talks about the precondition/postcondition behavior. Note that strictly speaking any valid 4xx status code could be used with those, its not just restricted to 403. But for all the CalDAV valid-xxx preconditions, 403 seems the most appropriate. In any case the rules for 412 apply - 412 is only returned when evaluation of the condition request headers indicate an error. I saw the 403 when using conditional headers. -- Ticket URL: <https://trac.calendarserver.org/ticket/273#comment:6> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0