Skip to content
This repository has been archived by the owner. It is now read-only.

Support 'component'(=VEVENT,VTODO) parameter in getcontenttype properties of PROPFIND results #239

macosforgebot opened this issue Aug 14, 2008 · 4 comments


Copy link

@macosforgebot macosforgebot commented Aug 14, 2008

helge@… originally submitted this as ticket:303

Small wish: could iCalServer set the 'component' property in resource content-types? This would make in-place filtering of PROPFIND results easier:


 Content-Type:text/calendar; charset=UTF-8; component=vevent


In Outlook we need to map a single calendar collection to two (or three) Outlook folders, eg "Calendar (Events)" and "Calendar (Tasks)". In Outlook each folder has a distinct type (its either tasks or events, never both).

So when we do a PROPFIND on a CalDAV calendar which supports both (calendar-component-set: VEVENT+VTODO), tasks and events (and journals ...), we currently just get the generic text/calendar type. We need to fetch the content to decide whether the item is relevant or not for a specific Outlook folder type. If the server would report the contained component-type, we could avoid that annoyingly hard work ;-)


PS: obviously the client can't (and shouldn't) rely on that parameter, but its a relevant optimization.

Copy link

@macosforgebot macosforgebot commented Sep 10, 2008

@wsanchez originally submitted this as comment:1:⁠ticket:303

  • Priority changed from 5: Not set to 3: Important
  • Milestone set to 2.x

This seems reasonable to me.

Copy link

@macosforgebot macosforgebot commented Oct 28, 2008

@wsanchez originally submitted this as comment:2:⁠ticket:303

Copy link

@macosforgebot macosforgebot commented Oct 26, 2009

@wsanchez originally submitted this as comment:3:⁠ticket:303

  • Milestone changed from CalendarServer-2.x to Later

Pushing to Later. If you have a patch, I'll pull it back in.

Copy link

@macosforgebot macosforgebot commented Apr 6, 2015

@wsanchez originally submitted this as comment:7:⁠ticket:303

  • Status changed from new to closed
  • Resolution set to Not to be fixed

Expiring old bugs with unknown impact

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.