Import events and todos in iCalendar format in to a calendar.
|calid||string||N|| Identifier of a calendar to which to import events and todos. The calid is the value given by the server as X-NSCP-
|N||Current user's default calendar calid|
|content-in||string||N||Content type of input data. Only text/calendar is supported.||N||text/calendar|
|dtend|| Date Time string in UTC
||N|| End time and date of the events and todos to import.
A value of 0 means import all components from the start date to the last date in the file.
|dtstart|| Date Time string in UTC
||N|| Start time and date of events and todos to import.
A value of 0 means import all components from the earliest date in the file to the end date.
|id||unique identifier string||N||The session identifier. Required unless the calendar is public.||Y||N/A|
Use this command to import to the specified calendar events and todos that have previously been exported to a file using the export command.
You must use this command with an HTTP POST message, unlike other commands that can be used with an HTTP GET message. You attach the file containing the exported events and todos to the POST message. This file must be in iCalendar (.ics) format.
If you do not specify either the starting or ending date, or you pass in 0 as the value for dtstart and dtend, the command adds all events and todos in the file to the specified calendar. If you specify a starting and ending date, the command imports only events and todos in the file that fall within the time range. Specify starting and ending dates in UTC time, which is indicated by the Z at the end of the date-time string.
If the operation is successful, the error number of 0 is appended to the error string. On failure, it returns the error code 77, BAD_IMPORT_ARGUMENTS. For a complete list of error codes, see Calendar Server WCAP 7.0 (WCAPbis) Error Codes.
The following POST message imports the attached iCalendar file to the calendar /home/jdoe/calendar/ using the import command. The session ID is required:
The following HTML form creates such a POST message, attaching a file that the user specifies: