CalDAV Component

Properties Methods Events Config Settings Errors

The CalDAV Component implements an easy-to-use interface to the Calendaring Extensions to the Web Distributed Authoring and Versioning protocol (WebDAV). In this manner the CalDAV protocol specifies a standard way of accessing, managing, and sharing calendaring and scheduling information based on the iCalendar format.

Syntax

IPWorks.Caldav

Remarks

The CalDAV Component supports both plaintext and SSL/TLS connections. When connecting over SSL/TLS the SSLServerAuthentication event allows you to check the server identity and other security attributes. The SSLStatus event provides information about the SSL handshake. Additional SSL related settings are also supported via the Config method.

The component allows remote management of calendar events and collections of events (the calendar itself), including creation, deletion, listing, copying, and moving. Resource locking is also supported.

The GetCalendarReport method will list the event resources contained in the calendar, and the ReportFilter can be used to limit the results returned. The EventDetails event will be fired for each matching calendar resource. You may also request a report containing a list of times that the owner is free or busy using the GetFreeBusyReport. The FreeBusy event will fire for each entry received, and the data fired in the event will also be stored in the FreeBusy property.

Single events can be added to a calendar (or updated) using the PutCalendarEvent method, and can be retrieved via the GetCalendarEvent method. Events may be copied or moved with the CopyCalendarEvent and MoveCalendarEvent.

Depth is used to determine which resources or properties are retrieved from the server. A depth of ResourceOnly will return only the resource associated with ResourceURI, or its properties. A depth of Infinity will return all resources contained within hierarchy, or their collective properties.

Note: Some servers (such as IIS 7.5) may not support a depth of Infinity by default and may return a HTTP 403 Forbidden response.

The following properties are used when creating a request with PutCalendarEvent or ExportICS, and will be filled after calling GetCalendarEvent or ImportICS. These will also be available from inside the EventDetails event, which is fired for each event received from the CalDAV server in response to a GetCalendarReport.

Alarms
Attendees
Categories
Classification
Completed
Created
CustomProperties
Depth
Description
DisplayName
Duration
EndDate
EventType
LastModified
Location
Organizer
Priority
Recurrence
Sequence
StartDate
Status
Summary
Timestamp
Timezone
Transparency
UID
URL

Each method that acts on the calendar takes a ResourceURI parameter, which points to either an event resource or to the calendar itself. Event resources have a URI that ends with a filename and the ".ics" extension. Calendar resources end in a directory path. The following methods all act on events, and thus their ResourceURI parameters must terminate in a filename with the ".ics" extension:

CopyCalendarEvent
DeleteCalendarEvent
MoveCalendarEvent
GetCalendarEvent
PutCalendarEvent

These methods all act upon the calendar collection resource (the calendar itself):

CreateCalendar
GetCalendarOptions
GetCalendarReport
GetFreeBusyReport

The LockCalendar and UnLockCalendar methods may operate on individual events or on the whole calendar.

There is no standard format for resource URIs. Google for instance, uses "https://www.google.com/calendar/dav/" plus your email address to access the default calendar. So "https://www.google.com/calendar/dav/username@gmail.com/" is the base URI for the default calendar. If you have multiple calendars, replace the email address portion above with the Id of the calendar, plus "@group.calendar.google.com/". For instance: "https://www.google.com/calendar/dav/ev3nkr4ua83jej7q32oumn5eeo@group.calendar.google.com/". For Google, calendar events are stored in the "/events/" path. To retrieve a report on a calendar, you'd add "/events/" to one of the above paths. For example: CalDAV.GetCalendarReport("https://www.google.com/calendar/dav/username@gmail.com/events/"); Leaving the "/events/" out of the URI will result in an HTTP protocol error: 405 Method not allowed.

To add or retrieve an event, add the UID of the event you're creating or retrieving plus ".ics" to the path. Note that when putting an event with the PutCalendarEvent method, if the resourceURI and the UID do not match Google will create the event using the UID stored in the UID property. The actual location of will be newly added event will be returned in a "Location" header. This is the resource URI you must use to retrieve the event with GetCalendarEvent. For example: CalDAV.UID = "1234567890"; CalDAV.PutCalendarEvent("https://www.google.com/calendar/dav/username@gmail.com/events/1234567890.ics");

Yahoo uses a different format for CalDAV access. Yahoo's ResourceURIs always start with "https://caldav.calendar.yahoo.com/dav/" plus your user name, plus "/Calendar/" plus the name of your calendar. For instance: "https://caldav.calendar.yahoo.com/dav/username/Calendar/Your_Name" for the default calendar. (Yahoo uses your name to create the default calendar). When using the CreateCalendar event to create a new calendar, replace "Your_Name" in the URI with the desired name of your new calendar. Event resources are located directly under the "/Calendar/Calendar_Name/" path. Like Google, the UID and filename portion of the resource URI must match, but Yahoo will actually return an HTTP protocol error if they differ. The examples below show a few possible transactions: CalDAVS1.User = "username"; CalDAVS1.Password = "password"; CalDAV.DisplayName = "My Hockey Calendar"; CalDAV.CreateCalendar("https://caldav.calendar.yahoo.com/dav/username/Calendar/Hockey_Calendar/"); CalDAV.StartDate = "20100401T040000"; CalDAV.EndDate = "20100401T060000"; CalDAV.UID = "qwerty1234567"; CalDAV.Summary = "First Practice"; CalDAV.Location = "Rink on 1st and main"; CalDAV.EventType = vEvent; CalDAV.PutCalendarEvent("https://caldav.calendar.yahoo.com/dav/username/Calendar/Hockey_Calendar/qwerty1234567.ics"); CalDAV.GetCalendarReport("https://caldav.calendar.yahoo.com/dav/username/Calendar/Hockey_Calendar/");

Property List

The following is the full list of the properties of the component with short descriptions. Click on the links for further details.


Alarms	An alarm related to the event.
Attendees	Defines one or more participants that have been invited to the event.
Authorization	This property includes the Authorization string to be sent to the server.
AuthScheme	The authentication scheme to use when server authentication is required.
Categories	Used to specify categories or subtypes of the calendar event.
Classification	Defines the access classification for a calendar component.
Completed	Date and time that a to-do was actually completed.
Connected	This shows whether the component is connected.
Cookies	This property includes a collection of cookies.
Created	Date and time calendar information created.
CustomProperties	List of extra properties that may be used to extend the functionality of this component.
Depth	The depth associated with the current operation.
Description	Provides a complete description of the calendar event.
DisplayName	Provides the display name of the calendar being created.
DueDate	Specifies the due date for a calendar event.
Duration	Duration of the calendar event.
EndDate	Specifies the date and time that a calendar event ends.
ETag	Identifier returned by the CalDAV server which is used to synchronize edits.
EventType	Indicates the type of calendar object resource.
Firewall	A set of properties related to firewall access.
FollowRedirects	This property determines what happens when the server issues a redirect.
FreeBusy	Specifies the times when the calendar owner is free or busy.
Idle	The current status of the component.
LastModified	The date and time that the information associated with the calendar event was last revised in the calendar store.
LocalHost	The name of the local host or user-assigned IP interface through which connections are initiated or accepted.
Location	Defines the intended venue for the activity defined by a calendar component.
LockProperties	Fields used when locking and unlocking a calendar resource.
Organizer	Defines the organizer of a calendar event.
OtherHeaders	This property includes other headers as determined by the user (optional).
ParsedHeaders	This property includes a collection of headers returned from the last request.
Password	This property includes a password if authentication is to be used.
Priority	Defines the relative priority for a calendar event.
Proxy	A set of properties related to proxy access.
Recurrence	Defines the recurrence set for the event.
ReportFilter	Criteria used to filter reports.
Sequence	Defines the revision sequence number of the event within a sequence of revisions.
SSLAcceptServerCert	Instructs the component to unconditionally accept the server certificate that matches the supplied certificate.
SSLCert	The certificate to be used during SSL negotiation.
SSLProvider	This specifies the SSL/TLS implementation to use.
SSLServerCert	The server certificate for the last established connection.
StartDate	Specifies the date and time that an event begins.
Status	Defines the overall status or confirmation for the calendar event.
StatusLine	This property is the first line of the last server response.
Summary	Defines a short summary or subject for the calendar event.
Timeout	A timeout for the component.
Timestamp	Specifies the date and time that the instance of the event was created.
Timezone	Specifies a time zone on a calendar collection.
Transparency	Defines whether or not an event is transparent to busy time searches.
UID	A persistent, globally unique identifier for the calendar event.
URL	Location of the event resource on the CalDAV server.
User	This property includes a user name if authentication is to be used.

Method List

The following is the full list of the methods of the component with short descriptions. Click on the links for further details.


addCookie	This method adds a cookie and the corresponding value to the outgoing request headers.
addCustomProperty	Adds a form variable and the corresponding value.
config	Sets or retrieves a configuration setting.
copyCalendarEvent	Copy events to a new location.
createCalendar	Creates a new calendar collection resource.
deleteCalendarEvent	Delete a resource or collection.
doEvents	Processes events from the internal message queue.
exportICS	Generates an event from the properties in the iCal (.ICS) format.
getCalendarEvent	Retrieves a single event from the CalDAV server.
getCalendarOptions	Retrieves options for the ResourceURI to determines whether it supports calendar access.
getCalendarReport	Generates a report on the indicated calendar collection resource.
getFreeBusyReport	Generates a report as to when the calendar owner is free and/or busy.
importICS	Imports calendar data (contained in an ICS file) into the component's property list.
interrupt	Interrupt the current method.
lockCalendar	Obtain a lock for a specified calendar resource.
moveCalendarEvent	Moves one calendar resource to a new location.
putCalendarEvent	Adds a calendar resource at the specified ResourceURI using the CalDAV PUT method.
reset	Reset the component.
unLockCalendar	Unlocks a calendar resource.

Event List

The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.


Connected	This event is fired immediately after a connection completes (or fails).
ConnectionStatus	This event is fired to indicate changes in the connection state.
Disconnected	This event is fired when a connection is closed.
EndTransfer	Fired when a document finishes transferring.
Error	Fired when information is available about errors during data delivery.
EventDetails	Fires for each calendar event received.
FreeBusy	Fires for each Free/Busy element received in the response.
Header	This event is fired every time a header line comes in.
Log	This event fires once for each log message.
Redirect	This event is fired when a redirection is received from the server.
SetCookie	This event is fired for every cookie set by the server.
SSLServerAuthentication	Fired after the server presents its certificate to the client.
SSLStatus	Fired when secure connection progress messages are available.
StartTransfer	Fired when a document starts transferring (after the headers).
Status	This event is fired when the HTTP status line is received from the server.
Transfer	This event is fired while a document transfers (delivers document).

Config Settings

The following is a list of config settings for the component with short descriptions. Click on the links for further details.


AuthScheme	The authentication scheme to use for server authorization.
BuildEvent	Builds the current event for a multi-event calendar entry.
EndCalendar	Signifies the end of a multi-event calendar entry.
ExpandRecurringEvents	Instructs the component to return all instances of a recurring event within a timeframe.
ListCalendars	Instructs the component list all the calendars for the current user.
ListCalendarsResultCount	Provides the number of calendars found when listing.
ListCalendarsResultDisplayName[i]	Provides the name of a listed calendar.
ListCalendarsResultURL[i]	Provides the URL of a listed calendar.
ProductId	Specifies the identifier for the product that created the iCalendar object.
RecurrenceExceptionDatesAttrs	Specifies the attributes for the exception dates of a recurring event.
StartCalendar	Signifies the beginning of a multi-event calendar entry.
EncodeURL	If set to true the URL will be encoded by the component.
IsDir[i]	Whether or not the resource at the specified index is a directory.
MaxResources	Instructs component to save the amount of resources specified that are returned by the server after a ListDirectory call has been made.
QueryPropertyNames	Instructs component explicitly request certain properties when calling ListDirectory.
AcceptEncoding	Used to tell the server which types of content encodings the client supports.
AllowHTTPCompression	This property enables HTTP compression for receiving data.
AllowHTTPFallback	Whether HTTP/2 connections are permitted to fallback to HTTP/1.1.
AllowNTLMFallback	Whether to allow fallback from Negotiate to NTLM when authenticating.
Append	Whether to append data to LocalFile.
Authorization	The Authorization string to be sent to the server.
BytesTransferred	Contains the number of bytes transferred in the response data.
ChunkSize	Specifies the chunk size in bytes when using chunked encoding.
CompressHTTPRequest	Set to true to compress the body of a PUT or POST request.
EncodeURL	If set to True the URL will be encoded by the component.
FollowRedirects	Determines what happens when the server issues a redirect.
GetOn302Redirect	If set to True the component will perform a GET on the new location.
HTTP2HeadersWithoutIndexing	HTTP2 headers that should not update the dynamic header table with incremental indexing.
HTTPVersion	The version of HTTP used by the component.
IfModifiedSince	A date determining the maximum age of the desired document.
KeepAlive	Determines whether the HTTP connection is closed after completion of the request.
KerberosSPN	The Service Principal Name for the Kerberos Domain Controller.
LogLevel	The level of detail that is logged.
MaxHeaders	Instructs component to save the amount of headers specified that are returned by the server after a Header event has been fired.
MaxHTTPCookies	Instructs component to save the amount of cookies specified that are returned by the server when a SetCookie event is fired.
MaxRedirectAttempts	Limits the number of redirects that are followed in a request.
NegotiatedHTTPVersion	The negotiated HTTP version.
OtherHeaders	Other headers as determined by the user (optional).
ProxyAuthorization	The authorization string to be sent to the proxy server.
ProxyAuthScheme	The authorization scheme to be used for the proxy.
ProxyPassword	A password if authentication is to be used for the proxy.
ProxyPort	Port for the proxy server (default 80).
ProxyServer	Name or IP address of a proxy server (optional).
ProxyUser	A user name if authentication is to be used for the proxy.
SentHeaders	The full set of headers as sent by the client.
StatusCode	The status code of the last response from the server.
StatusLine	The first line of the last response from the server.
TransferredData	The contents of the last response from the server.
TransferredDataLimit	The maximum number of incoming bytes to be stored by the component.
TransferredHeaders	The full set of headers as received from the server.
TransferredRequest	The full request as sent by the client.
UseChunkedEncoding	Enables or Disables HTTP chunked encoding for transfers.
UseIDNs	Whether to encode hostnames to internationalized domain names.
UsePlatformDeflate	Whether to use the platform implementation to decompress compressed responses.
UsePlatformHTTPClient	Whether or not to use the platform HTTP client.
UseProxyAutoConfigURL	Whether to use a Proxy auto-config file when attempting a connection.
UserAgent	Information about the user agent (browser).
CloseStreamAfterTransfer	If true, the component will close the upload or download stream after the transfer.
ConnectionTimeout	Sets a separate timeout value for establishing a connection.
FirewallAutoDetect	Tells the component whether or not to automatically detect and use firewall system settings, if available.
FirewallHost	Name or IP address of firewall (optional).
FirewallListener	If true, the component binds to a SOCKS firewall as a server (TCPClient only).
FirewallPassword	Password to be used if authentication is to be used when connecting through the firewall.
FirewallPort	The TCP port for the FirewallHost;.
FirewallType	Determines the type of firewall to connect through.
FirewallUser	A user name if authentication is to be used connecting through a firewall.
KeepAliveInterval	The retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received.
KeepAliveTime	The inactivity time in milliseconds before a TCP keep-alive packet is sent.
Linger	When set to True, connections are terminated gracefully.
LingerTime	Time in seconds to have the connection linger.
LocalHost	The name of the local host through which connections are initiated or accepted.
LocalPort	The port in the local host where the component binds.
MaxLineLength	The maximum amount of data to accumulate when no EOL is found.
MaxTransferRate	The transfer rate limit in bytes per second.
ProxyExceptionsList	A semicolon separated list of hosts and IPs to bypass when using a proxy.
TCPKeepAlive	Determines whether or not the keep alive socket option is enabled.
TcpNoDelay	Whether or not to delay when sending packets.
UseIPv6	Whether to use IPv6.
UseNTLMv2	Whether to use NTLM V2.
LogSSLPackets	Controls whether SSL packets are logged when using the internal security API.
ReuseSSLSession	Determines if the SSL session is reused.
SSLCACerts	A newline separated list of CA certificate to use during SSL client authentication.
SSLCipherStrength	The minimum cipher strength used for bulk encryption.
SSLContextProtocol	The protocol used when getting an SSLContext instance.
SSLEnabledCipherSuites	The cipher suite to be used in an SSL negotiation.
SSLEnabledProtocols	Used to enable/disable the supported security protocols.
SSLEnableRenegotiation	Whether the renegotiation_info SSL extension is supported.
SSLIncludeCertChain	Whether the entire certificate chain is included in the SSLServerAuthentication event.
SSLKeyLogFile	The location of a file where per-session secrets are written for debugging purposes.
SSLNegotiatedCipher	Returns the negotiated cipher suite.
SSLNegotiatedCipherStrength	Returns the negotiated cipher suite strength.
SSLNegotiatedCipherSuite	Returns the negotiated cipher suite.
SSLNegotiatedKeyExchange	Returns the negotiated key exchange algorithm.
SSLNegotiatedKeyExchangeStrength	Returns the negotiated key exchange algorithm strength.
SSLNegotiatedVersion	Returns the negotiated protocol version.
SSLServerCACerts	A newline separated list of CA certificate to use during SSL server certificate validation.
SSLTrustManagerFactoryAlgorithm	The algorithm to be used to create a TrustManager through TrustManagerFactory.
TLS12SignatureAlgorithms	Defines the allowed TLS 1.2 signature algorithms when SSLProvider is set to Internal.
TLS12SupportedGroups	The supported groups for ECC.
TLS13KeyShareGroups	The groups for which to pregenerate key shares.
TLS13SignatureAlgorithms	The allowed certificate signature algorithms.
TLS13SupportedGroups	The supported groups for (EC)DHE key exchange.
AbsoluteTimeout	Determines whether timeouts are inactivity timeouts or absolute timeouts.
FirewallData	Used to send extra data to the firewall.
InBufferSize	The size in bytes of the incoming queue of the socket.
OutBufferSize	The size in bytes of the outgoing queue of the socket.
BuildInfo	Information about the product's build.
GUIAvailable	Whether or not a message loop is available for processing events.
LicenseInfo	Information about the current license.
MaskSensitive	Whether sensitive data is masked in log messages.
UseDaemonThreads	Whether threads created by the component are daemon threads.
UseInternalSecurityAPI	Whether or not to use the system security libraries or an internal implementation.

Alarms Property (CalDAV Component)

An alarm related to the event.

Syntax


public CalAlarmList getAlarms();


public void setAlarms(CalAlarmList alarms);

Remarks

This property contains the information for an Alarm calendar component. An Alarm calendar component is a grouping of fields that set up a reminder or alarm for an event or to-do. For example, it may be used to define a reminder for a pending event or an overdue to-do.

Each CalAlarm calendar component MUST include the Action and Trigger fields. The Action field further constrains the CalAlarm in the following ways:

When the Action is aAudio, the alarm can optionally include an Attachment field, containing a base-64 encoded binary audio file to be played when the alarm is triggered.

When the Action is aDisplay, the alarm MUST also include the Message field, which contains the text to be displayed when the alarm is triggered.

When the Action is aEmail, the alarm MUST include the Message field, which contains the text to be used as the message body, the Subject field, which contains the text to be used as the message subject, and the Recipient field, which contains the email address of the person intended to receive the message.

An event may contain multiple alarms.

This property is filled from the response to a GetCalendarEvent, and is also used when creating an event to be added using the PutCalendarEvent method. However, when requesting a report using the GetCalendarReport method, the contents of this property will only be valid inside the EventDetails event.

Please refer to the CalAlarm type for a complete list of fields.

Attendees Property (CalDAV Component)

Defines one or more participants that have been invited to the event.

Syntax


public String getAttendees();


public void setAttendees(String attendees);

Default Value

Remarks

This property may contain a comma-separated list of attendees that have been invited to an event. Each email address should be in the mailto URI format (as defined in RFC2368). For instance: CalDAV.Attendees = "mailto:johnsmith@example.com,mailto:janedoe@test.com"

Authorization Property (CalDAV Component)

This property includes the Authorization string to be sent to the server.

Syntax


public String getAuthorization();


public void setAuthorization(String authorization);

Default Value

Remarks

If the Authorization property contains a nonempty string, an Authorization HTTP request header is added to the request. This header conveys Authorization information to the server.

A common use for this property is to specify OAuth authorization string.

This property is provided so that the HTTP component can be extended with other security schemes in addition to the authorization schemes already implemented by the component.

The AuthScheme property defines the authentication scheme used. In the case of HTTP Basic Authentication (default), every time User and Password are set, they are Base64 encoded, and the result is put in the Authorization property in the form "Basic [encoded-user-password]".

AuthScheme Property (CalDAV Component)

The authentication scheme to use when server authentication is required.

Syntax


public int getAuthScheme();


public void setAuthScheme(int authScheme);

Enumerated values:
  public final static int authBasic = 0;

  public final static int authDigest = 1;

  public final static int authProprietary = 2;

  public final static int authNone = 3;

  public final static int authNtlm = 4;

  public final static int authNegotiate = 5;

  public final static int authOAuth = 6;

Default Value

Remarks

This property will tell the component which type of authorization to perform when the User and Password properties are set.

This property should be set to authNone (3) when no authentication is to be performed.

By default, this property is authBasic (0), and if the User and Password properties are set, the component will attempt HTTP Basic Authentication. If AuthScheme is set to authDigest (1), authNtlm (4), or authNegotiate (5), then Digest, NTLM, or Windows Negotiate (Kerberos) authentication will be attempted instead.

If AuthScheme is set to authProprietary (2), then the authorization token must be supplied through the Authorization property.

If AuthScheme is set to authOAuth (6), then the authorization string must be supplied through the Authorization property.

Note: If you set the Authorization property and AuthScheme is not authProprietary or authOAuth, then the AuthScheme will be set automatically to authProprietary (2) by the component.

For security, changing the value of this property will cause the component to clear the values of User, Password, and Authorization.

Categories Property (CalDAV Component)

Used to specify categories or subtypes of the calendar event.

Syntax


public String getCategories();


public void setCategories(String categories);

Default Value

Remarks

This property is used to specify the categories or subtypes contained in a calendar event. The categories are useful in searching for an event of a particular type and/or category. Within the "VEVENT", "VTODO", or "VJOURNAL" calendar components, more than one category can be specified as a COMMA-separated list of categories. For example: CalDAV.CalendarEvents[0].Category = "APPOINTMENT,EDUCATION,MEETING";

Classification Property (CalDAV Component)

Defines the access classification for a calendar component.

Syntax


public String getClassification();


public void setClassification(String classification);

Default Value

Remarks

This property provides a method for capturing the access that the owner wishes to allow for the calendar component. Standard values include "PUBLIC", "PRIVATE", and "CONFIDENTIAL", but calendars may support additional values as well as user-defined values. If not specified, the default value is PUBLIC. Applications MUST treat Classification values that they do not recognize the same way as they would the PRIVATE value.

Completed Property (CalDAV Component)

Date and time that a to-do was actually completed.

Syntax


public String getCompleted();


public void setCompleted(String completed);

Default Value

Remarks

This property defines the date and time that a to-do was actually completed. This property is only applicable for the vTodo EventType. The date/time format is "YYYYMMDDThhmmss", where "T" indicates the break between date and time. You may also append a 1-character alpha code for the timezone. For instance, "20100104T123456Z" indicates January 4th, 2010 at 12:34:56 PM UTC.

Connected Property (CalDAV Component)

This shows whether the component is connected.

Syntax


public boolean isConnected();


public void setConnected(boolean connected);

Default Value

False

Remarks

This property is used to determine whether or not the component is connected to the remote host.

Note: It is recommended to use the Connect or Disconnect method instead of setting this property.

This property is not available at design time.

Cookies Property (CalDAV Component)

This property includes a collection of cookies.

Syntax


public HTTPCookieList getCookies();


public void setCookies(HTTPCookieList cookies);

Remarks

This property contains a collection of cookies. To add cookies to outgoing HTTP requests, add cookies (of type HTTPCookie) to this collection.

To see cookies that are set by the server, use the SetCookie event, which displays the cookies and their properties as set by the server. Those cookies also are added to Cookies.

MaxHTTPCookies can be used to control the maximum number of cookies saved.

This collection is indexed from 0 to size -1.

This property is not available at design time.

Please refer to the HTTPCookie type for a complete list of fields.

Created Property (CalDAV Component)

Date and time calendar information created.

Syntax


public String getCreated();


public void setCreated(String created);

Default Value

Remarks

This property specifies the date and time that the calendar information was created by the calendar user agent in the calendar store. The date/time format is "YYYYMMDDThhmmss", where "T" indicates the break between date and time. You may also append a 1-character alpha code for the timezone. For instance, "20100104T123456Z" indicates January 4th, 2010 at 12:34:56 PM UTC.

CustomProperties Property (CalDAV Component)

List of extra properties that may be used to extend the functionality of this component.

Syntax


public CalCustomPropList getCustomProperties();


public void setCustomProperties(CalCustomPropList customProperties);

Remarks

This property is used to add additional name/value pairs to the request. It is valid only for the PutCalendarEvent and CreateCalendar methods. You may use this property to submit any CalDAV fields that are not directly supported by this component. You may also use it to send custom properties that are specific on the calendar that you are using. Such custom properties normally start with "X-". For instance: CalDAV.CustomProperties.Add(new CalCustomProp("X-foo", "bar"));

Or alternatively: CalDAV.CustomProperties.Add(new CalCustomProp()); CalDAV.CustomProperties[0].Name = "X-hello"; CalDAV.CustomProperties[0].Value = "world";

The contents of the CustomProperties collection will only be added to the PutCalendarEvent or CreateCalendar requests. They will be ignored for all other methods.

This property is not available at design time.

Please refer to the CalCustomProp type for a complete list of fields.

Depth Property (CalDAV Component)

The depth associated with the current operation.

Syntax


public int getDepth();


public void setDepth(int depth);

Enumerated values:
  public final static int dpUnspecified = 0;

  public final static int dpResourceOnly = 1;

  public final static int dpImmediateChildren = 2;

  public final static int dpInfinity = 3;

Default Value

Remarks

This property defines how deep to operate within a collection. When performing certain operations on resource collections, the component will use Depth to instruct the server on how deep to operate within the collection. Depth is an enumerated type with the following possible values:


dpUnspecified (0)	The server will use the protocol default depth for the operation (this is normally "infinity").
dpResourceOnly (1)	The server will operate only on the collection resource URI, and not on any of its internal member resources.
dpImmediateChildren (2)	The server will operate on the collection resource URI and all of its immediate member resources (but on none of their member resources).
dpInfinity (3)	The server will recursively operate on the target resource URI and all of its internal member URIs through all levels of the collection hierarchy.

Depth is used when performing the following operations: LockCalendar, MoveCalendarEvent, CopyCalendarEvent, and GetCalendarReport

Description Property (CalDAV Component)

Provides a complete description of the calendar event.

Syntax


public String getDescription();


public void setDescription(String description);

Default Value

Remarks

This property provides a more complete description of the event than is provided by the Summary property. It is also used by the CreateCalendar method when creating a new calendar collection.

DisplayName Property (CalDAV Component)

Provides the display name of the calendar being created.

Syntax


public String getDisplayName();


public void setDisplayName(String displayName);

Default Value

Remarks

This property provides the name to be displayed for a calendar. This may or may not be defined on any calendar collection. It should be set before creating a new calendar collection via the CreateCalendar method.

DueDate Property (CalDAV Component)

Specifies the due date for a calendar event.

Syntax


public String getDueDate();


public void setDueDate(String dueDate);

Default Value

Remarks

This setting can be used to configure or obtain the due date for the selected calendar event.

Note: The format of this property should be the same as EndDate.

Duration Property (CalDAV Component)

Duration of the calendar event.

Syntax


public String getDuration();


public void setDuration(String duration);

Default Value

Remarks

This property contains the duration for a calendar event. Durations are represented by the format P<date>T<time>. The date component may contain a number of days or weeks (but not months or years), and the time component may consist of hours, minutes, and seconds. These are represented by an integer value followed by a letter representing the units, as specified by the table below:


P	is the duration designator (historically called "period") placed at the start of the duration representation.
W	is the week designator that follows the value for the number of weeks.
D	is the day designator that follows the value for the number of days.
T	is the time designator that precedes the time components of the representation.
H	is the hour designator that follows the value for the number of hours.
M	is the minute designator that follows the value for the number of minutes.
S	is the second designator that follows the value for the number of seconds.

For example, "P4DT12H30M5S" represents a duration of four days, twelve hours, thirty minutes, and five seconds. Unused date/time designators may be left out completely. (A five-minute duration may be represented as simply "PT5M"). Also note that "PT36H" and "P1DT12H" represent the same duration.

This format is based on ISO-8601, but unlike the ISO specification this duration property does not support durations measured in years or months.

EndDate Property (CalDAV Component)

Specifies the date and time that a calendar event ends.

Syntax


public String getEndDate();


public void setEndDate(String endDate);

Default Value

Remarks

This property specifies the date and time that a calendar event will end. The date/time format is "YYYYMMDDThhmmss", where "T" indicates the break between date and time. You may also append a 1-character alpha code for the timezone. For instance, "20100104T123456Z" indicates January 4th, 2010 at 12:34:56 PM UTC.

ETag Property (CalDAV Component)

Identifier returned by the CalDAV server which is used to synchronize edits.

Syntax


public String getETag();


public void setETag(String ETag);

Default Value

Remarks

This property identifies the state of the event in the calendar. An ETag is returned by the CalDAV server after a successful PutCalendarEvent request. Every time an event is updated, the ETag changes. This gives you the ability to determine if another user has changed the event you added.

You can use this ETag value to maintain a cache. If you submit a GetCalendarReport request with the ReturnCalendarData field set to False only the URI and ETags for each event in the calendar will be returned in the report. You can cache the ETag and URI locally, and then inspect the report for any changes and update only the events that have changed ETags.

When updating an event with the PutCalendarEvent method, you may add the ETag to the "If-Match" header (using OtherHeaders) in order to insure that you are not overwriting more recent changes on the server. For instance: calDAV.UID = "20110202T000000Z-6414-500-10112-204@nsoftest"; calDAV.StartDate = "20110202T000000Z"; calDAV.EndDate = "20110202T110000Z"; calDAV.TimeStamp = "20100301T000000Z"; calDAV.Summary = "Dinner with friends"; calDAV.Description = "Getting everyone together for some food and fun"; calDAV.Location = "The James Joyce Irish Pub"; calDAV.EventType = CaldavsEventTypes.vEvent; calDAV.OtherHeaders = "If-Match: 1900-1900\r\ n"; calDAV.PutCalendarEvent "https://caldav.calendar.yahoo.com/dav/user_name/Calendar/My_Calendar/20110202T000000Z-6414-500-10112-204@nsoftest.ics" If the current ETag for the above event is "1900-1900", then the above modification will work perfectly. However, if the event was modified on the Yahoo server, the ETag will not match and the above will fail with an HTTP Protocol error: "409 Conflict". In that case you should retrieve the event with GetCalendarEvent and update the most recent version.

EventType Property (CalDAV Component)

Indicates the type of calendar object resource.

Syntax


public int getEventType();


public void setEventType(int eventType);

Enumerated values:
  public final static int vEvent = 0;

  public final static int vTodo = 1;

  public final static int vJournal = 2;

  public final static int vFreeBusy = 3;

Default Value

Remarks

This property indicates the type of calendar object resource is used.

Firewall Property (CalDAV Component)

A set of properties related to firewall access.

Syntax


public Firewall getFirewall();


public void setFirewall(Firewall firewall);

Remarks

This is a Firewall-type property, which contains fields describing the firewall through which the component will attempt to connect.

Please refer to the Firewall type for a complete list of fields.

FollowRedirects Property (CalDAV Component)

This property determines what happens when the server issues a redirect.

Syntax


public int getFollowRedirects();


public void setFollowRedirects(int followRedirects);

Enumerated values:
  public final static int frNever = 0;

  public final static int frAlways = 1;

  public final static int frSameScheme = 2;

Default Value

Remarks

This property determines what happens when the server issues a redirect. Normally, the component returns an error if the server responds with an "Object Moved" message. If this property is set to frAlways (1), the new URL for the object is retrieved automatically every time.

If this property is set to frSameScheme (2), the new URL is retrieved automatically only if the URLScheme is the same; otherwise, the component throws an exception.

Note: Following the HTTP specification, unless this property is set to frAlways (1), automatic redirects will be performed only for GET or HEAD requests. Other methods potentially could change the conditions of the initial request and create security vulnerabilities.

Furthermore, if either the new URL server or port are different from the existing one, User and Password are also reset to empty. If, however, this property is set to frAlways (1), the same credentials are used to connect to the new server.

A Redirect event is fired for every URL the product is redirected to. In the case of automatic redirections, the Redirect event is a good place to set properties related to the new connection (e.g., new authentication parameters).

The default value is frNever (0). In this case, redirects are never followed, and the component throws an exception instead.

FreeBusy Property (CalDAV Component)

Specifies the times when the calendar owner is free or busy.

Syntax


public CalFreeBusyList getFreeBusy();

Remarks

This property may contain free/busy information in response to a GetFreeBusyReport request or after either a GetCalendarReport or a GetCalendarEvent request. In the latter case, this property will only contain data when the EventType is vFreeBusy.

This property is read-only.

Please refer to the CalFreeBusy type for a complete list of fields.

Idle Property (CalDAV Component)

The current status of the component.

Syntax


public boolean isIdle();

Default Value

True

Remarks

Idle will be False if the component is currently busy (communicating and/or waiting for an answer), and True at all other times.

This property is read-only.

LastModified Property (CalDAV Component)

The date and time that the information associated with the calendar event was last revised in the calendar store.

Syntax


public String getLastModified();


public void setLastModified(String lastModified);

Default Value

Remarks

This property contains the date and time that the information associated with the calendar event was last revised in the calendar store. This is analogous to the modification date and time for a file in the file system, and must be specified in the UTC time format: <date>T<time>Z, where date is in "YYYYMMDD" format and time is in "hhmmss" format. "T" is the delimiter between date and time, and "Z" is the UTC timezone indicator. For example, "20020119T13:23:56Z" is 1:23:56pm on January 19th, 2002. The date/time format is "YYYYMMDDThhmmss", where "T" indicates the break between date and time. You may also append a 1-character alpha code for the timezone. For instance, "20100104T123456Z" indicates January 4th, 2010 at 12:34:56 PM UTC.

LocalHost Property (CalDAV Component)

The name of the local host or user-assigned IP interface through which connections are initiated or accepted.

Syntax


public String getLocalHost();


public void setLocalHost(String localHost);

Default Value

Remarks

The LocalHost property contains the name of the local host as obtained by the gethostname() system call, or if the user has assigned an IP address, the value of that address.

In multi-homed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the component initiate connections (or accept in the case of server components) only through that interface.

If the component is connected, the LocalHost property shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multi-homed hosts (machines with more than one IP interface).

NOTE: LocalHost is not persistent. You must always set it in code, and never in the property window.

Location Property (CalDAV Component)

Defines the intended venue for the activity defined by a calendar component.

Syntax


public String getLocation();


public void setLocation(String location);

Default Value

Remarks

This property may be used to explicitly specify the venue, such as conference or meeting rooms, for the activity defined by a calendar component. An alternate representation may be specified using a URI that points to directory information with more structured specifications of the location. For example, the alternate representation may specify either an LDAP URL [RFC4516] pointing to an LDAP server entry or a CID URL [RFC2392] pointing to a MIME body part containing a Virtual-Information Card (vCard) [RFC2426] for the location.

LockProperties Property (CalDAV Component)

Fields used when locking and unlocking a calendar resource.

Syntax


public CalLock getLockProperties();


public void setLockProperties(CalLock lockProperties);

Remarks

This property used the LockType, Owner, Scope Timeout, and Tokens fields when locking and unlocking a calendar resource. You may lock the whole calendar, or only a single event within the calendar, depending on the URI you pass to LockCalendar or UnLockCalendar. After a successful LockCalendar operation, the component will the LockType, Owner, Scope Timeout, and Tokens fields to the values returned in the server's response. The lock Tokens are then passed along when you call CopyCalendarEvent or MoveCalendarEvent

Please refer to the CalLock type for a complete list of fields.

Organizer Property (CalDAV Component)

Defines the organizer of a calendar event.

Syntax


public String getOrganizer();


public void setOrganizer(String organizer);

Default Value

Remarks

This property is specified within the vEvent, vTodo, and vJournal calendar EventTypes to specify the organizer of a group-scheduled calendar entity. The property is specified within the vFreeBusy EventType to identify the calendar user requesting the free or busy time. When publishing a vFreeBusy EventType, the property is used to specify the calendar that the published busy time came from.

Each email address should be in the mailto URI format (as defined in RFC2368).

For instance: CalDAV.Organizer = "mailto:jane_doe@example.com";

OtherHeaders Property (CalDAV Component)

This property includes other headers as determined by the user (optional).

Syntax


public String getOtherHeaders();


public void setOtherHeaders(String otherHeaders);

Default Value

Remarks

This property can be set to a string of headers to be appended to the HTTP request headers created from other properties like ContentType and From.

The headers must follow the format Header: Value as described in the HTTP specifications. Header lines should be separated by CRLF ("\r\n") .

Use this property with caution. If this property contains invalid headers, HTTP requests may fail.

This property is useful for extending the functionality of the component beyond what is provided.

For CalDAV, the "If-Match" header is extremely useful. After adding a an event with PutCalendarEvent or retrieving an event with GetCalendarEvent, the ETag property will contain a value indicating the current state of the event. If you wish to update the event, you may pass this returned ETag in an "If-Match" header. If the event on the server has been modified since you retrieved it (and the ETag on the server has changed), then the PutCalendarEvent will fail with an HTTP Protocol Error: "409 Conflict", which indicates there is a conflict between the version you're trying to update and the current version on the sever. For instance: calDAV.OtherHeaders = "If-Match: 1900-1900\r\ n";

This property is not available at design time.

ParsedHeaders Property (CalDAV Component)

This property includes a collection of headers returned from the last request.

Syntax


public HeaderList getParsedHeaders();

Remarks

This property contains a collection of headers returned from the last request. Whenever headers are returned from the server, the headers are parsed into a collection of headers. Each Header in this collection contains information describing that header.

MaxHeaders can be used to control the maximum number of headers saved.

This collection is indexed from 0 to size -1.

This property is read-only and not available at design time.

Please refer to the Header type for a complete list of fields.

Password Property (CalDAV Component)

This property includes a password if authentication is to be used.

Syntax


public String getPassword();


public void setPassword(String password);

Default Value

Remarks

This property contains a password if authentication is to be used. If AuthScheme is set to HTTP Basic Authentication, the User and Password are Base64 encoded and the result is put in the Authorization configuration setting in the form "Basic [encoded-user-password]".

If AuthScheme is set to HTTP Digest Authentication, the User and Password properties are used to respond to the HTTP Digest Authentication challenge from the server.

If AuthScheme is set to NTLM, NTLM authentication will be attempted. If AuthScheme is set to NTLM and User and Password are empty, the component will attempt to authenticate using the current user's credentials.

Priority Property (CalDAV Component)

Defines the relative priority for a calendar event.

Syntax


public int getPriority();


public void setPriority(int priority);

Default Value

Remarks

This property defines the relative priority of a calendar event. The priority is specified as an integer in the range 0 to 9. A value of 0 specifies an undefined Priority. A value of 1 is the highest Priority. A value of 2 is the second highest Priority. Subsequent numbers specify a decreasing ordinal Priority. A value of 9 is the lowest Priority.

A Calendar User-Agent (CUA) with a three-level Priority scheme of "HIGH", "MEDIUM", and "LOW" is mapped into this property such that a property value in the range of 1 to 4 specifies "HIGH" Priority. A value of 5 is the normal or "MEDIUM" Priority. A value in the range of 6 to 9 is "LOW" Priority.

Proxy Property (CalDAV Component)

A set of properties related to proxy access.

Syntax


public Proxy getProxy();


public void setProxy(Proxy proxy);

Remarks

This property contains fields describing the proxy through which the component will attempt to connect.

Please refer to the Proxy type for a complete list of fields.

Recurrence Property (CalDAV Component)

Defines the recurrence set for the event.

Syntax


public CalRecurrence getRecurrence();


public void setRecurrence(CalRecurrence recurrence);

Remarks

This property defines the recurrence set for the event. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial StartDate property along with the Rule, Dates, ExceptionRule, and ExceptionDates fields contained within the recurring event. The StartDate property defines the first instance in the recurrence set. The starting date SHOULD match the pattern of the recurrence rule, if specified. The recurrence set generated with a start date that doesn't match the pattern of the rule is undefined. The final recurrence set is generated by gathering all of the start DATE-TIME values generated by any of the specified Rule and Dates fields, and then excluding any start DATE-TIME values specified by the ExceptionRule or ExceptionDates fields. This implies that DATE-TIME values specified by the ExceptionRule and ExceptionDates fields take precedence over those specified by inclusion properties (i.e., Dates and Rule). When duplicate instances are generated by the recurrence Rule and Dates fields, only one recurrence is considered. Duplicate instances are ignored.

Please refer to the CalRecurrence type for a complete list of fields.

ReportFilter Property (CalDAV Component)

Criteria used to filter reports.

Syntax


public CalReportFilter getReportFilter();


public void setReportFilter(CalReportFilter reportFilter);

Remarks

This property may be used to restrict the results of reports to only those that match your search criteria.The GetCalendarReport method will normally return the entire calendar collection at the specified ResourceURI. You can restrict results to only events within a specified time range (using StartDate and EndDate), to only recurring events within a specified time range (using RecurStart and RecurEnd), and to events with an alarm set to go off within a specified time range. (using AlarmStart and AlarmEnd). You can also restrict results to only those events which contain a specific Property (either by property name, or name and a specific value). The EventType property determines what kind of events are returned (events, todo lists, journal entries, or free/busy time).

Please refer to the CalReportFilter type for a complete list of fields.

Sequence Property (CalDAV Component)

Defines the revision sequence number of the event within a sequence of revisions.

Syntax


public int getSequence();


public void setSequence(int sequence);

Default Value

Remarks

This property defines the revision sequence number of the event within a sequence of revisions. When a calendar component is created its Sequence number is 0. It is incremented by the Organizer's Calendar User Agent (CUA) each time the Organizer makes a significant revision to the calendar event. Therefore, a Sequence number of 2 means the event has been revised twice.

The Organizer includes this property in a calendar event that it sends to an Attendees to specify the current version of the event. Likewise, the Attendees includes this property in an event that it sends to the Organizer to specify the version of the calendar component to which the Attendees is referring.

Note: Recurrence instances of a recurring event may have different sequence numbers.

SSLAcceptServerCert Property (CalDAV Component)

Instructs the component to unconditionally accept the server certificate that matches the supplied certificate.

Syntax


public Certificate getSSLAcceptServerCert();


public void setSSLAcceptServerCert(Certificate SSLAcceptServerCert);

Remarks

If it finds any issues with the certificate presented by the server, the component will normally terminate the connection with an error.

You may override this behavior by supplying a value for SSLAcceptServerCert. If the certificate supplied in SSLAcceptServerCert is the same as the certificate presented by the server, then the server certificate is accepted unconditionally, and the connection will continue normally.

Please note that this functionality is provided only for cases where you otherwise know that you are communicating with the right server. If used improperly, this property may create a security breach. Use it at your own risk.

Please refer to the Certificate type for a complete list of fields.

SSLCert Property (CalDAV Component)

The certificate to be used during SSL negotiation.

Syntax


public Certificate getSSLCert();


public void setSSLCert(Certificate SSLCert);

Remarks

The digital certificate that the component will use during SSL negotiation. Set this property to a valid certificate before starting SSL negotiation. To set a certificate, you may set the Encoded field to the encoded certificate. To select a certificate, use the store and subject fields.

Please refer to the Certificate type for a complete list of fields.

SSLProvider Property (CalDAV Component)

This specifies the SSL/TLS implementation to use.

Syntax


public int getSSLProvider();


public void setSSLProvider(int SSLProvider);

Enumerated values:
  public final static int sslpAutomatic = 0;

  public final static int sslpPlatform = 1;

  public final static int sslpInternal = 2;

Default Value

Remarks

This property specifies the SSL/TLS implementation to use. In most cases the default value of 0 (Automatic) is recommended and should not be changed. When set to 0 (Automatic) the component will select whether to use the platform implementation or the internal implementation depending on the operating system as well as the TLS version being used.

Possible values are:


0 (sslpAutomatic - default)	Automatically selects the appropriate implementation.
1 (sslpPlatform)	Uses the platform/system implementation.
2 (sslpInternal)	Uses the internal implementation.

Additional Notes

In most cases using the default value (Automatic) is recommended. The component will select a provider depending on the current platform.

When Automatic is selected the platform implementation is used by default. When TLS 1.3 is enabled via SSLEnabledProtocols the internal implementation is used.

SSLServerCert Property (CalDAV Component)

The server certificate for the last established connection.

Syntax


public Certificate getSSLServerCert();

Remarks

SSLServerCert contains the server certificate for the last established connection.

SSLServerCert is reset every time a new connection is attempted.

This property is read-only.

Please refer to the Certificate type for a complete list of fields.

StartDate Property (CalDAV Component)

Specifies the date and time that an event begins.

Syntax


public String getStartDate();


public void setStartDate(String startDate);

Default Value

Remarks

This property specifies the date and time that an event begins. The date/time format is "YYYYMMDDThhmmss", where "T" indicates the break between date and time. You may also append a 1-character alpha code for the timezone. For instance, "20100104T123456Z" indicates January 4th, 2010 at 12:34:56 PM UTC.

Status Property (CalDAV Component)

Defines the overall status or confirmation for the calendar event.

Syntax


public String getStatus();


public void setStatus(String status);

Default Value

Remarks

In a group-scheduled calendar component, the property is used by the Organizer to provide a confirmation of the event to the Attendees. For example in a vEvent EventType the Organizer can indicate that a meeting is tentative, confirmed, or canceled. For a vTodo EventType, the Organizer can indicate that an action item needs action, is completed, is in process or being worked on, or has been canceled. In a vJournal EventType, the Organizer can indicate that a journal entry is draft, final, or has been canceled or removed.

Statuses for a vEvent EventType:


TENTATIVE	Indicates event is tentative.
CONFIRMED	Indicates event is definite.
CANCELLED	Indicates event was canceled.

Statuses for a vTodo EventType:


NEEDS-ACTION	Indicates to-do needs action.
COMPLETED	Indicates to-do completed.
IN-PROCESS	Indicates to-do in process of.
CANCELLED	Indicates to-do was canceled.

Statuses for a vJournal EventType:


DRAFT	Indicates event is draft.
FINAL	Indicates event is final.
CANCELLED	Indicates event is removed.

StatusLine Property (CalDAV Component)

This property is the first line of the last server response.

Syntax


public String getStatusLine();

Default Value

Remarks

This property contains the first line of the last server response. This value can be used for diagnostic purposes. If an HTTP error is returned when calling a method of the component, the error string is the same as the StatusLine property.

The HTTP protocol specifies the structure of the StatusLine as follows: [HTTP version] [Result Code] [Description].

This property is read-only and not available at design time.

Summary Property (CalDAV Component)

Defines a short summary or subject for the calendar event.

Syntax


public String getSummary();


public void setSummary(String summary);

Default Value

Remarks

This property defines a short summary or subject for the calendar event.

Timeout Property (CalDAV Component)

A timeout for the component.

Syntax


public int getTimeout();


public void setTimeout(int timeout);

Default Value

Remarks

If the Timeout property is set to 0, all operations will run uninterrupted until successful completion or an error condition is encountered.

If Timeout is set to a positive value, the component will wait for the operation to complete before returning control.

The component will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not "freeze" and remains responsive.

If Timeout expires, and the operation is not yet complete, the component throws an exception.

Please note that by default, all timeouts are inactivity timeouts, i.e. the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.

The default value for the Timeout property is 60 seconds.

Timestamp Property (CalDAV Component)

Specifies the date and time that the instance of the event was created.

Syntax


public String getTimestamp();


public void setTimestamp(String timestamp);

Default Value

Remarks

This property specifies the date and time that the instance of the event was created. The date/time format is "YYYYMMDDThhmmss", where "T" indicates the break between date and time. You may also append a 1-character alpha code for the timezone. For instance, "20100104T123456Z" indicates January 4th, 2010 at 12:34:56 PM UTC.

Note: This property must be specified in UTC time format.

Timezone Property (CalDAV Component)

Specifies a time zone on a calendar collection.

Syntax


public CalTimezone getTimezone();


public void setTimezone(CalTimezone timezone);

Remarks

This property is used to specify the time zone the server should rely on to resolve "date" values and "date with local time" values (i.e., floating time) to "date with UTC time" values. The server will require this information to determine if a calendar component scheduled with "date" values or "date with local time" values overlap a time range specified in a GetCalendarReport. In the absence of this property, the server may rely on a time zone of its choosing.

This may be specified when adding or modifying an event with the PutCalendarEvent method, and can also specify the default timezone for the calendar when creating a new calendar collection via the CreateCalendar method.

This property may be filled from the response to a GetCalendarEvent, and can also be used when creating an event to be added using the PutCalendarEvent method. It is also optional when calling the CreateCalendar method. However, when requesting a report using the GetCalendarReport method, the contents of this property will only be valid inside the EventDetails event.

Please refer to the CalTimezone type for a complete list of fields.

Transparency Property (CalDAV Component)

Defines whether or not an event is transparent to busy time searches.

Syntax


public String getTransparency();


public void setTransparency(String transparency);

Default Value

Remarks

This property defines whether or not an event is transparent to busy time searches. Time Transparency is the characteristic of an event that determines whether it appears to consume time on a calendar. Events that consume actual time for the individual or resource associated with the calendar SHOULD be recorded as "OPAQUE", allowing them to be detected by free/busy time searches. Other events, which do not take up the individual's (or resource's) time SHOULD be recorded as "TRANSPARENT", making them invisible to free/ busy time searches.

Custom transparency values may or may not be supported by your calendar implementation, but all implementations will support the "OPAQUE" and "TRANSPARENT" values.

UID Property (CalDAV Component)

A persistent, globally unique identifier for the calendar event.

Syntax


public String getUID();


public void setUID(String UID);

Default Value

Remarks

This property contains a persistent, globally unique identifier. The generator of the identifier MUST guarantee that the identifier is unique. There are several algorithms that can be used to accomplish this. A good method to assure uniqueness is to put the domain name or a domain literal IP address of the host on which the identifier was created on the right-hand side of an "@", and on the left-hand side, put a combination of the current calendar date and time of day (i.e., formatted in as a date/time value) along with some other currently unique (perhaps sequential) identifier available on the system (for example, a process id number). Using a date/time value on the left-hand side and a domain name or domain literal on the right-hand side makes it possible to guarantee uniqueness since no two hosts should be using the same domain name or IP address at the same time. Though other algorithms will work, it is recommended that the right-hand side contain some domain identifier (either of the host itself or otherwise) such that the generator of the message identifier can guarantee the uniqueness of the left-hand side within the scope of that domain.

NOTE: Some CalDAV servers (Yahoo for example) require that the UID and the filename portion of the Resource URI match. For example, if the UID is "hello_world" then the ResourceURI parameter of the PutCalendarEvent should be "https://caldav.calendar.yahoo.com/dav/user_name/Calendar/My_Calendar/hello_world.ics". If the UID and filename portion of the URI do not match, the Yahoo CalDAV server will return a "302 Found" response indicating that the requested resource resides under a different URI. (Meaning the event was not added to the calendar)

URL Property (CalDAV Component)

Location of the event resource on the CalDAV server.

Syntax


public String getURL();

Default Value

Remarks

This property is read-only, and will be filled with the location of the event resource for each event returned. This will only be returned in response to a GetCalendarReport transaction.

This property is read-only.

User Property (CalDAV Component)

This property includes a user name if authentication is to be used.

Syntax


public String getUser();


public void setUser(String user);

Default Value

Remarks

This property contains a user name if authentication is to be used. If AuthScheme is set to HTTP Basic Authentication, The User and Password are Base64 encoded, and the result is put in the Authorization property in the form "Basic [encoded-user-password]".

If AuthScheme is set to HTTP Digest Authentication, the User and Password properties are used to respond to the HTTP Digest Authentication challenge from the server.

If AuthScheme is set to NTLM, NTLM authentication will be attempted. If AuthScheme is set to NTLM, and User and Password are empty, the component will attempt to authenticate using the current user's credentials.

AddCookie Method (Caldav Component)

This method adds a cookie and the corresponding value to the outgoing request headers.

Syntax

public void addCookie(String cookieName, String cookieValue);

Remarks

This property adds a cookie and the corresponding value to the outgoing request headers. Please refer to the Cookies property for more information on cookies and how they are managed.

AddCustomProperty Method (Caldav Component)

Adds a form variable and the corresponding value.

Syntax

public void addCustomProperty(String varName, String varValue);

Remarks

This property adds a form variable and the corresponding value. For information on form variables and how they are managed, please refer to the CustomProperties collection.

Example using the AddCustomProperty method:

CalDAVControl.Reset() CalDAVControl.AddCustomProperty("propname1", "propvalue1") CalDAVControl.AddCustomProperty("propname2", "propvalue2") Example using the CustomProperties collection: CalDAVControl.Reset() CalDAVControl.CustomProperties.Add(new CalCustomProp("propname1", "propvalue1")) CalDAVControl.CustomProperties.Add(new CalCustomProp("propname2", "propvalue2"))

Config Method (Caldav Component)

Sets or retrieves a configuration setting.

Syntax

public String config(String configurationString);

Remarks

Config is a generic method available in every component. It is used to set and retrieve configuration settings for the component.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.

To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.

CopyCalendarEvent Method (Caldav Component)

Copy events to a new location.

Syntax

public void copyCalendarEvent(String sourceResourceURI, String destinationResourceURI);

Remarks

The CopyCalendarEvent method will copy the resource indicated by SourceResourceURI to a new location under the resource indicated by DestinationResourceURI.

This method is associated with the Depth property. If Depth is set to "0", the component will copy only SourceResourceURI. If Depth is set to "infinity", the component will copy SourceResourceURI and its entire subtree to the relative locations.

If the user has acquired a LockCalendar of infinite depth on either DestinationResourceURI or any collection it is under, SourceResourceURI will be added to that lock.

Note that neither Yahoo nor Google CalDAV servers support locking, copying, or moving calendar resources.

CreateCalendar Method (Caldav Component)

Creates a new calendar collection resource.

Syntax

public void createCalendar(String resourceURI);

Remarks

The CreateCalendar method creates a new calendar collection resource. A server MAY restrict calendar collection creation to particular collections. Creating calendar collections is not supported by all CalDAV servers. Some calendar stores only support one calendar per user (or principal), and those are typically pre-created for each account.

The following properties are used to create a new calendar collection resource:

Description
DisplayName
Timezone

To successfully create a calendar, the ResourceURI cannot already exist, and must point to a valid location where a new calendar can be created. The DAV:bind privilege MUST be granted to the current user on the parent collection of the specified ResourceURI.

The following example shows how to create a simple new calendar collection resource with Yahoo Calendar. CalDAVS1.DisplayName = "Testing Create Calendar method"; CalDAVS1.Description = "Test Calendar"; CalDAVS1.CreateCalendar("https://caldav.calendar.yahoo.com/dav/userid/Calendar/TestCal1");

Note that Google does not support creating a new calendar through CalDAV. It must be created through the Google calendar web interface.

DeleteCalendarEvent Method (Caldav Component)

Delete a resource or collection.

Syntax

public void deleteCalendarEvent(String resourceURI);

Remarks

This method behaves independently of the Depth property. It is used to delete the resource or collection specified by ResourceURI. If ResourceURI denotes a non-collection resource, it is first removed from any collection in which it is contained, it is then removed from the server. If ResourceURI denotes a collection, the server behaves as if the command were issued with an infinite depth (i.e., all internal member URIs denoting single resources or collections are deleted).

DoEvents Method (Caldav Component)

Processes events from the internal message queue.

Syntax

public void doEvents();

Remarks

When DoEvents is called, the component processes any available events. If no events are available, it waits for a preset period of time, and then returns.

ExportICS Method (Caldav Component)

Generates an event from the properties in the iCal (.ICS) format.

Syntax

public String exportICS();

Remarks

The ExportICS method is used to create a calendar object and export it in the iCal/ICS format, which can then be saved to disk and imported using any calendar software, even those that do not support CalDAV. The ExportICS method will create the exact same data as the PutCalendarEvent method sends when adding or updating an event to a calendar.

Note that if ExportICS is called immediately after a successful GetCalendarEvent, the unmodified calendar returned from the CalDAV server will be returned. However if any properties are changed between the GetCalendarEvent and ExportICS calls, the component will generate and return a brand new event.

Alarms
Attendees
Categories
Classification
Completed
Created
CustomProperties
Depth
Description
DisplayName
Duration
EndDate
EventType
LastModified
Location
Organizer
Priority
Recurrence
Sequence
StartDate
Status
Summary
Timestamp
Timezone
Transparency
UID
URL

GetCalendarEvent Method (Caldav Component)

Retrieves a single event from the CalDAV server.

Syntax

public void getCalendarEvent(String resourceURI);

Remarks

This method retrieves a single event from a CalDAV server. The ResourceURI points to the exact location of the iCal (*.ics) file you wish to retrieve. (If you do not know the URL of the event you need, you can use the GetCalendarReport method along with the ReportFilter property to find it.)

The event will be fetched using the WebDAV GET method. The full response is delivered through the Transfer event and the HTTP response headers through the Header event. After an event is retrieved with this method, the component parses the calendar data into properties. You may then edit these properties and use PutCalendarEvent to update the calendar event resource.

Alarms
Attendees
Categories
Classification
Completed
Created
CustomProperties
Depth
Description
DisplayName
Duration
EndDate
EventType
LastModified
Location
Organizer
Priority
Recurrence
Sequence
StartDate
Status
Summary
Timestamp
Timezone
Transparency
UID
URL

GetCalendarOptions Method (Caldav Component)

Retrieves options for the ResourceURI to determines whether it supports calendar access.

Syntax

public void getCalendarOptions(String resourceURI);

Remarks

This method sends an OPTIONS HTTP request to the indicated ResourceURI. The server will respond with an 200 OK HTTP message, and the supported options will fire one-by-one in the Header event. If a server supports CalDAV calendar access, the "DAV" header will contain the string "calendar-access". The allowable CalDAV and WebDAV methods may also be returned in the "Allow" header.

For instance, the following headers may be returned from a call to the GetCalendarOptions method:


Field	Value
Allow	OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE
Allow	PROPFIND, PROPPATCH, LOCK, UNLOCK, REPORT, ACL
DAV	1, 2, access-control, calendar-access
Date	Sat, 11 Nov 2006 09:32:12 GMT
Content-Length	0

Since the "DAV" header contains "calendar-access", CalDAV is supported on this ResourceURI.

GetCalendarReport Method (Caldav Component)

Generates a report on the indicated calendar collection resource.

Syntax

public void getCalendarReport(String resourceURI);

Remarks

This method is used to send a calendar-query request to the calendar located at the specified ResourceURI. The ReportFilter can be used to filter out and return only the calendar events you wish to receive. The response to a calendar-query report will be parsed by the component, and information about the individual events contained within shall be fired in the EventDetails event.

Alarms
Attendees
Categories
Classification
Completed
Created
CustomProperties
Depth
Description
DisplayName
Duration
EndDate
EventType
LastModified
Location
Organizer
Priority
Recurrence
Sequence
StartDate
Status
Summary
Timestamp
Timezone
Transparency
UID
URL

For example: CalDAV.User = "myusername"; CalDAV.Password = "mypassword"; CalDAV.ReportFilter.StartDate = "20090101T000000Z"; CalDAV.ReportFilter.EndDate = "20091231T230000Z"; CalDAV.GetCalendarReport("https://caldav.calendar.yahoo.com/dav/username/Calendar/default_calendar/"); The following code inside the EventDetails event will print the start and end time as well as the summary for each event: void CalDAV_OnEventDetails(object sender, CaldavsEventDetailsEventArgs e) { Console.WriteLine(CalDAV.Summary + ": " + CalDAV.StartDate + " to " + CalDAV.EndDate); } The output from the above code will look something like this:

	Carolina Hurricanes vs. Colorado Avalanche: 20090222T150000 to 20090222T180000
	Lone Rider Brewery Tour: 20091107T124500 to 20091107T134500
	Salsa Dancing: 20090927T154500 to 20090927T181500
	Superbowl Party: 20090201T170000 to 20090202T000000
	Kathy's Birthday: 20090608T010000 to 20090608T020000
	Dinner at Shannon's: 20091001T183000 to 20091001T203000
	Carolina Rollergirls match: 20090411T170000 to 20090411T180000

GetFreeBusyReport Method (Caldav Component)

Generates a report as to when the calendar owner is free and/or busy.

Syntax

public void getFreeBusyReport(String resourceURI);

Remarks

This method sends a free-busy-query request to the calendar at the specified ResourceURI. . The CalDAV server will return a list of FREEBUSY elements, which will be fired in the FreeBusy event and also stored in the FreeBusy collection. Each FREEBUSY element contains a type (BUSY, FREE, BUSY-TENTATIVE, etc.) and a date range.

Note that the StartDate field is required for a Free/Busy report. The EndDate field is optional. These are the only two ReportFilters used by the GetFreeBusyReport request, all other filters will be ignored.

Note that Google Calendar does not currently support Free/Busy reporting.

ImportICS Method (Caldav Component)

Imports calendar data (contained in an ICS file) into the component's property list.

Syntax

public void importICS(String calendarData);

Remarks

This method is used to load calendar data from an external source into the component. You may then submit this data with a call to PutCalendarEvent. If you edit any of the component properties between importing and calling PutCalendarEvent, the component will re-generate the PUT request itself. If no properties are changed, the imported data will be submitted unaltered when calling PutCalendarEvent.

As the calendar data is imported, the component will scan CalendarData for any calendar events. Each time a calendar event is discovered, the EventDetails event will fire, and the calendar event properties will be updated.

After ImportICS completes, the calendar event properties will be set to the most recent calendar event found in CalendarData.

Interrupt Method (Caldav Component)

Interrupt the current method.

Syntax

public void interrupt();

Remarks

If there is no method in progress, Interrupt simply returns, doing nothing.

LockCalendar Method (Caldav Component)

Obtain a lock for a specified calendar resource.

Syntax

public void lockCalendar(String resourceURI);

Remarks

This method will request a new lock to be placed on ResourceURI in the user's name so that only the user can operate on it. The method is linked to a number of properties that it uses to generate the lock request:


Owner	The principle that will own the lock.
Scope	The scope of the lock. The component only currently supports locks of scope "exclusive" and "shared".
Timeout	The amount of time that the lock is allowed to exist before `ResourceURI` is automatically unlocked by the server.
Tokens	The lock itself. If the user sets this before making the request, the timeout on the existing lock will be refreshed (reset to 0). Otherwise, a new set of lock tokens will be returned.
LockType	The type of lock. The component only currently supports of type "write".

After a successful call to the LockCalendar method the component will receive the new lock values, which it will parse and store in the lock properties.

This method is associated with the Depth property. If Depth is set to "0", the component will lock only ResourceURI and its properties. If Depth is set to "infinity", the component will lock ResourceURI and its entire subtree.

If MoveCalendarEvent or CopyCalendarEvent are used to place a resource or collection in a location under a resource locked with "infinity", the new resource or collection will be added to the lock. Any lock on a collection will prevent non-lock owners from adding resources to that collection.

Note that while the Yahoo CalDAV server does accept LockCalendar and UnLockCalendar requests, the server does not respect resource locks (either on events or on the entire calendar). The Google CalDAV sever does not support either of these requests, and will respond with an HTTP protocol error: 405 Method Not Allowed. Also, neither Yahoo nor Google CalDAV servers support copying or moving calendar resources.

MoveCalendarEvent Method (Caldav Component)

Moves one calendar resource to a new location.

Syntax

public void moveCalendarEvent(String sourceResourceURI, String destinationResourceURI);

Remarks

This method will move the resource indicated by SourceResourceURI to a new location under the resource indicated by DestinationResourceURI.

This method is associated with the Depth property. If Depth is set to "0", the component will move only SourceResourceURI. If Depth is set to "infinity", the component will move SourceResourceURI and its entire subtree to locations relative to it.

If the user has acquired a lock of infinite depth (via LockCalendar) on either DestinationResourceURI or any collection it is under, SourceResourceURI will be added to that lock.

Note that neither Yahoo nor Google CalDAV servers support locking, copying, or moving calendar resources.

PutCalendarEvent Method (Caldav Component)

Adds a calendar resource at the specified ResourceURI using the CalDAV PUT method.

Syntax

public void putCalendarEvent(String resourceURI);

Remarks

This method adds a new event to the calendar collection at the specified ResourceURI. The ResourceURI must be a fully qualified URL to the location on the CalDAV server to which this event will be saved. If the ResourceURI already exists, the event at that URI will be overwritten.

NOTE: Some CalDAV servers (Yahoo for example) require that the UID and the filename portion of the URI match. For example, if the UID is "hello_world" then the ResourceURI parameter of the PutCalendarEvent should be "https://caldav.calendar.yahoo.com/dav/user_name/Calendar/My_Calendar/hello_world.ics". If the UID and filename portion of the URI do not match, the Yahoo CalDAV server will return a "302 Found" response indicating that the requested resource resides under a different URI. (Meaning the event was not added to the calendar)

Alarms
Attendees
Categories
Classification
Completed
Created
CustomProperties
Depth
Description
DisplayName
Duration
EndDate
EventType
LastModified
Location
Organizer
Priority
Recurrence
Sequence
StartDate
Status
Summary
Timestamp
Timezone
Transparency
UID
URL

Reset Method (Caldav Component)

Reset the component.

Syntax

public void reset();

Remarks

This method will reset the component's properties to their default values.

UnLockCalendar Method (Caldav Component)

Unlocks a calendar resource.

Syntax

public void unLockCalendar(String resourceURI);

Remarks

This method unlocks a calendar resource. Before calling UnLockCalendar on a particular calendar resource, the Tokens property must be set to the lock tokens for ResourceURI. The method will remove the lock, allowing other users or non-privileged users to access and operate on the file.

Connected Event (Caldav Component)

This event is fired immediately after a connection completes (or fails).

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void connected(CaldavConnectedEvent e) {}
  ...
}

public class CaldavConnectedEvent {
  public int statusCode;

  public String description;

}

Remarks

If the connection is made normally, StatusCode is 0 and Description is "OK".

If the connection fails, StatusCode has the error code returned by the Transmission Control Protocol (TCP)/IP stack. Description contains a description of this code. The value of StatusCode is equal to the value of the error.

Please refer to the Error Codes section for more information.

ConnectionStatus Event (Caldav Component)

This event is fired to indicate changes in the connection state.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void connectionStatus(CaldavConnectionStatusEvent e) {}
  ...
}

public class CaldavConnectionStatusEvent {
  public String connectionEvent;

  public int statusCode;

  public String description;

}

Remarks

The ConnectionStatus event is fired when the connection state changes: for example, completion of a firewall or proxy connection or completion of a security handshake.

The ConnectionEvent parameter indicates the type of connection event. Values may include the following:


	Firewall connection complete.
	Secure Sockets Layer (SSL) or S/Shell handshake complete (where applicable).
	Remote host connection complete.
	Remote host disconnected.
	SSL or S/Shell connection broken.
	Firewall host disconnected.

StatusCode has the error code returned by the Transmission Control Protocol (TCP)/IP stack. Description contains a description of this code. The value of StatusCode is equal to the value of the error.

Disconnected Event (Caldav Component)

This event is fired when a connection is closed.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void disconnected(CaldavDisconnectedEvent e) {}
  ...
}

public class CaldavDisconnectedEvent {
  public int statusCode;

  public String description;

}

Remarks

If the connection is broken normally, StatusCode is 0 and Description is "OK".

If the connection is broken for any other reason, StatusCode has the error code returned by the Transmission Control Protocol (TCP/IP) subsystem. Description contains a description of this code. The value of StatusCode is equal to the value of the TCP/IP error.

Please refer to the Error Codes section for more information.

EndTransfer Event (Caldav Component)

Fired when a document finishes transferring.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void endTransfer(CaldavEndTransferEvent e) {}
  ...
}

public class CaldavEndTransferEvent {
  public int direction;

}

Remarks

The EndTransfer event is fired when the document text finishes transferring from the server to the local host.

The Direction parameter shows whether the client (0) or the server (1) is sending the data.

Error Event (Caldav Component)

Fired when information is available about errors during data delivery.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void error(CaldavErrorEvent e) {}
  ...
}

public class CaldavErrorEvent {
  public int errorCode;

  public String description;

}

Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the component throws an exception.

The ErrorCode parameter contains an error code, and the Description parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

EventDetails Event (Caldav Component)

Fires for each calendar event received.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void eventDetails(CaldavEventDetailsEvent e) {}
  ...
}

public class CaldavEventDetailsEvent {
  public String resourceURI;

  public String responseStatus;

  public String ETag;

  public String calendarData;

}

Remarks

This event fires for each VEVENT, VTODO, VJOURNAL, or VFREEBUSY event received in response to a GetCalendarReport request. The ResourceURI parameter indicates the location of this particular event on the CalDAV server, and the ETag parameter is used to indicate the current state of the calendar event. If the ETag is different from the value you have cached for the current ResourceURI, it means the event has changed on the server since the last time you updated your cache. ResponseStatus indicates the HTTP status of CalDAV server received when attempting to retrieve this particular ResourceURI when it was building the report. The CalendarData parameter contains the raw calendar entry as returned by the CalDAV server. This data is also parsed into the following properties, and are valid for the current ResourceURI only inside this event.

Alarms
Attendees
Categories
Classification
Completed
Created
CustomProperties
Depth
Description
DisplayName
Duration
EndDate
EventType
LastModified
Location
Organizer
Priority
Recurrence
Sequence
StartDate
Status
Summary
Timestamp
Timezone
Transparency
UID
URL

Note that for a large calendar you may not wish to return the full contents of each calendar event, as this could be a substantially large amount of data. In this case, set the ReturnCalendarData field to false, and only the ResourceURI, ResponseStatus, and ETag parameters will be returned by the CalDAV server for each calendar event. The contents of the event will not be returned, and the CalendarData parameter will be empty.

*The ResourceURI and the URL property are not the same. The URL property is an iCal field, and the ResourceURI is the actual location of the resource on the CalDAV server. Some CalDAV servers may force the URL to match the ResourceURI, but the URL should be treated as a separate user-defined entity by the user, and it should not be expected to match the ResourceURI. Likewise, ResponseStatus and Status are not the same. Status is the status of the event (TENTATIVE, CONFIRMED, CANCELLED, etc). ResponseStatus is the HTTP status received when the CalDAV server attempted to retrieve the current event when constructing a report.

FreeBusy Event (Caldav Component)

Fires for each Free/Busy element received in the response.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void freeBusy(CaldavFreeBusyEvent e) {}
  ...
}

public class CaldavFreeBusyEvent {
  public String busyType;

  public String busyRange;

}

Remarks

This event fires for each FREEBUSY element received in response to a GetFreeBusyReport request. The FBTYPE will be contained in the BusyType parameter, and the FREEBUSY value itself will be contained in the BusyRange parameter. The Free/Busy information will also be stored in the FreeBusy collection.

Header Event (Caldav Component)

This event is fired every time a header line comes in.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void header(CaldavHeaderEvent e) {}
  ...
}

public class CaldavHeaderEvent {
  public String field;

  public String value;

}

Remarks

The Field parameter contains the name of the HTTP header (which is the same as it is delivered). The Value parameter contains the header contents.

If the header line being retrieved is a continuation header line, then the Field parameter contains "" (empty string).

Log Event (Caldav Component)

This event fires once for each log message.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void log(CaldavLogEvent e) {}
  ...
}

public class CaldavLogEvent {
  public int logLevel;

  public String message;

  public String logType;

}

Remarks

This event fires once for each log message generated by the component. The verbosity is controlled by the LogLevel setting.

LogLevel indicates the level of message. Possible values are as follows:


0 (None)	No events are logged.
1 (Info - default)	Informational events are logged.
2 (Verbose)	Detailed data are logged.
3 (Debug)	Debug data are logged.

The value 1 (Info) logs basic information, including the URL, HTTP version, and status details.

The value 2 (Verbose) logs additional information about the request and response.

The value 3 (Debug) logs the headers and body for both the request and response, as well as additional debug information (if any).

Message is the log entry.

LogType identifies the type of log entry. Possible values are as follows:

"Info"
"RequestHeaders"
"ResponseHeaders"
"RequestBody"
"ResponseBody"
"ProxyRequest"
"ProxyResponse"
"FirewallRequest"
"FirewallResponse"

Redirect Event (Caldav Component)

This event is fired when a redirection is received from the server.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void redirect(CaldavRedirectEvent e) {}
  ...
}

public class CaldavRedirectEvent {
  public String location;

  public boolean accept;

}

Remarks

This event is fired in cases in which the client can decide whether or not to continue with the redirection process. The Accept parameter is always True by default, but if you do not want to follow the redirection, Accept may be set to False, in which case the component throws an exception. Location is the location to which the client is being redirected. Further control over redirection is provided in the FollowRedirects property.

SetCookie Event (Caldav Component)

This event is fired for every cookie set by the server.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void setCookie(CaldavSetCookieEvent e) {}
  ...
}

public class CaldavSetCookieEvent {
  public String name;

  public String value;

  public String expires;

  public String domain;

  public String path;

  public boolean secure;

}

Remarks

The SetCookie event is fired for every Set-Cookie: header received from the HTTP server.

The Name parameter contains the name of the cookie, with the corresponding value supplied in the Value parameter.

The Expires parameter contains an expiration time for the cookie (if provided by the server). The time format used is "Weekday, DD-Mon-YY HH:MM:SS GMT". If the server does not provide an expiration time, the Expires parameter will be an empty string. In this case, the convention is to drop the cookie at the end of the session.

The Domain parameter contains a domain name to limit the cookie to (if provided by the server). If the server does not provide a domain name, the Domain parameter will be an empty string. The convention in this case is to use the server specified in the URL (URLServer) as the cookie domain.

The Path parameter contains a path name to limit the cookie to (if provided by the server). If the server does not provide a cookie path, the Path parameter will be an empty string. The convention in this case is to use the path specified in the URL (URLPath) as the cookie path.

The Secure parameter specifies whether the cookie is secure. If the value of this parameter is True, the cookie value must be submitted only through a secure (HTTPS) connection.

SSLServerAuthentication Event (Caldav Component)

Fired after the server presents its certificate to the client.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void SSLServerAuthentication(CaldavSSLServerAuthenticationEvent e) {}
  ...
}

public class CaldavSSLServerAuthenticationEvent {
  public byte[] certEncoded;

  public String certSubject;

  public String certIssuer;

  public String status;

  public boolean accept;

}

Remarks

During this event, the client can decide whether or not to continue with the connection process. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether or not to continue.

When Accept is False, Status shows why the verification failed (otherwise, Status contains the string OK). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.

SSLStatus Event (Caldav Component)

Fired when secure connection progress messages are available.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void SSLStatus(CaldavSSLStatusEvent e) {}
  ...
}

public class CaldavSSLStatusEvent {
  public String message;

}

Remarks

The event is fired for informational and logging purposes only. This event tracks the progress of the connection.

StartTransfer Event (Caldav Component)

Fired when a document starts transferring (after the headers).

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void startTransfer(CaldavStartTransferEvent e) {}
  ...
}

public class CaldavStartTransferEvent {
  public int direction;

}

Remarks

The StartTransfer event is fired when the document text starts transferring from the server to the local host.

The Direction parameter shows whether the client (0) or the server (1) is sending the data.

Status Event (Caldav Component)

This event is fired when the HTTP status line is received from the server.

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void status(CaldavStatusEvent e) {}
  ...
}

public class CaldavStatusEvent {
  public String HTTPVersion;

  public int statusCode;

  public String description;

}

Remarks

HTTPVersion is a string containing the HTTP version string as returned from the server (e.g., "1.1").

StatusCode contains the HTTP status code (e.g., 200), and Description the associated message returned by the server (e.g., "OK").

Transfer Event (Caldav Component)

This event is fired while a document transfers (delivers document).

Syntax

public class DefaultCaldavEventListener implements CaldavEventListener {
  ...
  public void transfer(CaldavTransferEvent e) {}
  ...
}

public class CaldavTransferEvent {
  public int direction;

  public long bytesTransferred;

  public int percentDone;

  public byte[] text;

}

Remarks

The Text parameter contains the portion of the document text being received. It is empty if data are being posted to the server.

The BytesTransferred parameter contains the number of bytes transferred in this Direction since the beginning of the document text (excluding HTTP response headers).

The Direction parameter shows whether the client (0) or the server (1) is sending the data.

The PercentDone parameter shows the progress of the transfer in the corresponding direction. If PercentDone can not be calculated the value will be -1.

Note: Events are not re-entrant. Performing time-consuming operations within this event will prevent it from firing again in a timely manner and may affect overall performance.

CalAlarm Type

An alarm related to a calendar event.

Remarks

An Alarm calendar component is a grouping of fields that set up a reminder or an alarm for an event or to-do. For example, it may be used to define a reminder for a pending event or an overdue to-do.

The CalAlarm calendar component MUST include the Action and Trigger fields. The Action field further constrains the CalAlarm in the following ways:

When the Action is aAudio, the alarm can optionally include an Attachment field, containing a base-64 encoded binary audio file to be played when the alarm is triggered.

When the Action is aDisplay, the alarm MUST also include the Message field, which contains the text to be displayed when the alarm is triggered.

Fields

Action
int
Default Value: 0

This field determines what the CalDAV server will do when the alarm Trigger is reached. The following table explains the possible alarm actions:


aAudio (0)	Specifies an alarm that causes a sound to be played to alert the user. You may attach a custom sound file using the Attachment field.
aDisplay (1)	Specifies an alarm that causes a visual alert to be displayed to the user. If Action is set to this value, you must also set the Message field with the message to be displayed.
aEmail (2)	Instructs the CalDAV sever to email a specified Recipient. In this case, the Message field will contain the message body of the email and the Subject field should contain the subject line.

Attachment
String
Default Value: ""

This field contains a sound file attached to the alarm. If the Action is set to aAudio, this field may optionally contain a base-64 encoded binary sound file to be played. The AttachmentType field indicates the data type of the attached file.

AttachmentType
String
Default Value: ""

This field contains the MIME-Type of the attachment. If the Action is set to aAudio or aEmail the Attachment property may optionally contain a base-64 binary encoded attachment. The AttachmentType field is used to tell the CalDAV server what type of binary file it is receiving. This field is a standard MIME content type, in the format "type/sub-type". The most common audio types are shown in the table below:


AttachmentType	File Extension	Description
audio/basic	au, snd	basic audio, 8-bit u-law PCM.
audio/mid	mid, rmi	MIDI music data
audio/mpeg	mp2, mp3	MPEG-1 Audio Layer II and III.
audio/x-aiff	aiff, aif, aifc	Macintosh audio format
audio/x-mp4a-latm	m4a	MPEG-4 Audio
audio/x-pn-realaudio	ra, ram	Realaudio
audio/x-wav	wav	Microsoft waveform audio
audio/x-ms-wma	wma	Windows Media Audio (Microsoft)

You may use standard MIME content-types for any other file type you wish to submit in the Attachment field. If Attachment is specified but AttachmentType is left blank, no format type will be submitted with the Attachment and the CalDAV server may (or may not) attempt to determine the data type itself.

Duration
String
Default Value: ""

This field contains the interval between repeating alarms. This field is only used when an alarm is set to Repeat multiple times. It is specified in the form of a Duration data type. Durations are represented by the format P<date>T<time>. The date component may contain a number of days or weeks (but not months or years), and the time component may consist of hours, minutes, and seconds. These are represented by an integer value followed by a letter representing the units, as specified by the table below:


P	is the duration designator (historically called "period") placed at the start of the duration representation.
W	is the week designator that follows the value for the number of weeks.
D	is the day designator that follows the value for the number of days.
T	is the time designator that precedes the time components of the representation.
H	is the hour designator that follows the value for the number of hours.
M	is the minute designator that follows the value for the number of minutes.
S	is the second designator that follows the value for the number of seconds.

This format is based on ISO-8601, but unlike the ISO specification this duration property does not support durations measured in years or months.

The following is an example of an alarm that repeats 4 additional times after the initial Trigger, with a 5-minute delay between each alarm: CalDav.Trigger = "-PT10M"; CalDAV.Alarm.Repeat = 4; CalDAV.Duration = "PT5M" CalDAV.Action = aDisplay;

If Duration is specified, Repeat MUST also be specified.

Message
String
Default Value: ""

This field contains a message used to alert the user when this alarm is triggered. If the Action is set to aDisplay, this field must contain the message that is to be displayed to the user. If Action is set to aEmail this field will contain the message body of the email that is sent to the Recipient. For instance: CalDAV.Alarm.Action = aEmail; CalDAV.Alarm.Recipient = "mailto:john_doe@example.com"; CalDAV.Alarm.Message = "A draft agenda needs to be sent out to the attendees to the weekly managers meeting (MGR-LIST)."; CalDAV.Alarm.Subject = "REMINDER: Send agenda for weekly staff meeting."; or CalDAV.Alarm.Action = aDisplay; CalDAV.Alarm.Message = "REMINDER: Send agenda for weekly staff meeting."; Message is not used for the aAudio alarm Action.

Recipient
String
Default Value: ""

This field contains the email address of the person to be alerted when this alarm is triggered. If Action is set to aEmail this field must contain one or more comma-separated email addresses to which the email alarm is to be sent. For instance: CalDAV.Alarm.Action = aEmail; CalDAV.Alarm.Recipient = "mailto:john_doe@example.com"; CalDAV.Alarm.Message = "A draft agenda needs to be sent out to the attendees to the weekly managers meeting (MGR-LIST)."; CalDAV.Alarm.Subject = "REMINDER: Send agenda for weekly staff meeting."; Recipient is not used for the aAudio or aDisplay alarm Actions.

Repeat
int
Default Value: 0

This field contains the number of times the alarm is to be repeated after the initial trigger.

This field defines the number of times an alarm should be repeated after its initial Trigger. If the alarm triggers more than once, then this property MUST be specified along with the Duration field.

Subject
String
Default Value: ""

This field contains the subject of the message used to alert the user when this alarm is triggered. If Action is set to aEmail this field will contain the subject the email that is sent to the Recipient. For instance: CalDAV.Alarm.Action = aEmail; CalDAV.Alarm.Recipient = "mailto:john_doe@example.com"; CalDAV.Alarm.Message = "A draft agenda needs to be sent out to the attendees to the weekly managers meeting (MGR-LIST)."; CalDAV.Alarm.Subject = "REMINDER: Send agenda for weekly staff meeting."; Subject is not used for the aAudio or aDisplay alarm Actions.

Trigger
String
Default Value: ""

This field contains the time when the alarm is triggered.

The Trigger is represented as a duration relative to the start of an event. The format is (+/-)P<date>T<time>. The date component may contain a number of days or weeks (but not months or years), and the time component may consist of hours, minutes, and seconds. These are represented by an integer value followed by a letter representing the units, as specified by the table below:


P	is the duration designator (historically called "period") placed at the start of the duration representation.
W	is the week designator that follows the value for the number of weeks.
D	is the day designator that follows the value for the number of days.
T	is the time designator that precedes the time components of the representation.
H	is the hour designator that follows the value for the number of hours.
M	is the minute designator that follows the value for the number of minutes.
S	is the second designator that follows the value for the number of seconds.

Either a positive or negative duration may be specified for the Trigger field. An alarm with a positive duration is triggered after the associated start of the event (or to-do). An alarm with a negative duration is triggered before the start of the event. For instance, the following code instructs an alarm to fire 10 minutes before the event starts: CalDAV.Alarm.Trigger = "-PT10M"

Constructors

public CalAlarm();

public CalAlarm( trigger,  action);

CalCustomProp Type

Name/Value pair of custom properties to add to the request.

Remarks

This type describes a form variable that is to be posted to the Resource URI when Putting an event or creating a new calendar. The type contains fields which describe this variable's name, value, and attribute.

Fields

Attribute
String
Default Value: ""

This field contains an optional attribute of the custom property.

Name
String
Default Value: ""

This field contains the textual name of the custom property.

Value
String
Default Value: ""

This field contains the value of the custom property.

Constructors

public CalCustomProp();

public CalCustomProp( name,  value);

public CalCustomProp( name,  value,  attribute);

CalFreeBusy Type

Describes a single free/busy element in the calendar event.

Remarks

This type describes a FREEBUSY element contained in the calendar data. Each FREEBUSY element will contain a BusyType (BUSY, FREE, BUSY-TENTATIVE, etc.) and a BusyRange, which describes the date and time range for the FREEBUSY element.

Fields

BusyRange
String (read-only)
Default Value: ""

Contains the date/time range when the calendar owner is busy. The format for this field is either "DATETIME/DATETIME" or "DATETIME/DURATION"

The date/time format is "YYYYMMDDThhmmss", where "T" indicates the break between date and time. You may also append a 1-character alpha code for the timezone. For instance, "20100104T123456Z" indicates January 4th, 2010 at 12:34:56 PM UTC.

Durations are represented by the format P<date>T<time>. The date component may contain a number of days or weeks (but not months or years), and the time component may consist of hours, minutes, and seconds. These are represented by an integer value followed by a letter representing the units, as specified by the table below:


P	is the duration designator (historically called "period") placed at the start of the duration representation.
W	is the week designator that follows the value for the number of weeks.
D	is the day designator that follows the value for the number of days.
T	is the time designator that precedes the time components of the representation.
H	is the hour designator that follows the value for the number of hours.
M	is the minute designator that follows the value for the number of minutes.
S	is the second designator that follows the value for the number of seconds.

This format is based on ISO-8601, but unlike the ISO specification this duration property does not support durations measured in years or months.

BusyType
String (read-only)
Default Value: ""

Indicates the busy status of the corresponding BusyRange. A calendar may use custom values for the BusyType, but the standard values include:

BUSY
FREE
BUSY-TENTATIVE
BUSY-UNAVAILABLE

Constructors

public CalFreeBusy();

CalLock Type

Group of fields used when locking and unlocking a calendar resource.

Remarks

LockType, Owner, Scope Timeout, and Tokens are used when locking and unlocking a calendar resource. You may lock the whole calendar, or only a single event within the calendar, depending on the URI you use when locking. After a successful LockCalendar operation, the component will set all of these fields to the values returned in the server's response. The lock Tokens are then passed along when copying or moving a calendar event.

Fields

LockType
String
Default Value: "write"

The type of the current resource lock.

Before the calendar resource can be locked, the LockType may be set to the type of lock being requested. Currently, the component only supports requesting locks of type "write", although the protocol defines an optional "read" lock. After a successful LockCalendar operation, the component will set the LockType field to the correct value returned in the server's response.

Owner
String
Default Value: ""

The principle that owns the current resource lock.

Before the calendar resource can be locked, the Lock Owner may be set to the name of a principle or group of principles that will own the lock. If no owner is specified, the server will automatically associate the lock with the requesting principle. After a successful LockCalendar operation, the component will set the Owner field to the correct value returned in the server's response.

Scope
String
Default Value: ""

The scope of the current resource lock.

Before the calendar resource can be locked, the Lock Scope may be set to the type of scope needed for the lock. Currently the component will only allow two types of scopes to be requested:


"exclusive"	The lock belongs exclusively to the requesting principle. No other principle may modify the locked resource URI.
"shared"	The locked resource may not be modified by non-trusted principles. Users who have access rights, however, may request a shared lock which they can then use to modify or operate on the resource.

If no scope is specified, the protocol default scope, "exclusive", will be requested. After a successful LockCalendar operation, the component will set the Scope field to the correct value returned in the server's response.

Timeout
int
Default Value: 0

The time to live for the current resource lock.

Before the calendar resource can be locked, the Lock Timeout may be set to a specific amount of time needed for the locked operation to take place. The timeout is used to determine how long the lock may exist before the server automatically unlocks the resource URI. If Timeout of 0 is specified, the server will use a default timeout. After a successful LockCalendar operation, the component will set the Lock Timeout field to the correct value returned in the server's response.

Tokens
String
Default Value: ""

The lock string to be used when submitting operations on a locked resource.

Before the calendar resource can be locked, the Lock Tokens may be set to the tokens returned by a previous lock operation. This is useful when renewing a timeout. The server will respond with a new timeout value, which will be stored in Timeout. If the lock request is not a lock refresh, Tokens must be empty, and will be parsed out of the server response after a successful LockCalendar operation.

Constructors

public CalLock();

CalRecurrence Type

Defines the recurrence set for an event.

Remarks

The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial StartDate property along with the Rule, Dates, ExceptionRule, and ExceptionDates fields contained within the recurring event. The StartDate property defines the first instance in the recurrence set. The starting date SHOULD match the pattern of the recurrence rule, if specified. The recurrence set generated with a start date that doesn't match the pattern of the rule is undefined. The final recurrence set is generated by gathering all of the start DATE-TIME values generated by any of the specified Rule and Dates fields, and then excluding any start DATE-TIME values specified by the ExceptionRule or ExceptionDates fields. This implies that DATE-TIME values specified by the ExceptionRule and ExceptionDates fields take precedence over those specified by inclusion properties (i.e., Dates and Rule). When duplicate instances are generated by the recurrence Rule and Dates fields, only one recurrence is considered. Duplicate instances are ignored.

Fields

Dates
String
Default Value: ""

Individual dates on which the event will recur.

This field is used if you wish to denote specific, individual dates on which the event recurs. If you have an event that occurs monthly or weekly or on some other time interval, use the Rule field instead.

This field is filled after retrieving a calendar event, and is also used to create an event to put on the server. However, when requesting a report the contents of this field will only be valid inside the CalDAV EventDetails event.

ExceptionDates
String
Default Value: ""

Defines the list of DATE-TIME exceptions to the recurrence set.

If the ExceptionDates and ExceptionRule are specified, they are used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial StartDate property along with the Rule, Dates, ExceptionRule, and ExceptionDates fields contained within the recurring event. The StartDate property defines the first instance in the recurrence set. The starting date SHOULD match the pattern of the recurrence rule, if specified. The recurrence set generated with a start date that doesn't match the pattern of the rule is undefined. The final recurrence set is generated by gathering all of the start DATE-TIME values generated by any of the specified Rule and Dates fields, and then excluding any start DATE-TIME values specified by the ExceptionRule or ExceptionDates fields. This implies that DATE-TIME values specified by the ExceptionRule and ExceptionDates fields take precedence over those specified by inclusion properties (i.e., Dates and Rule). When duplicate instances are generated by the recurrence Rule and Dates fields, only one recurrence is considered. Duplicate instances are ignored.

ExceptionRule
String
Default Value: ""

Defines a rule or repeating pattern for an exception to the recurrence set.

This value type is a structured value consisting of a list of one or more recurrence grammar parts. Each rule part is defined by a NAME=VALUE pair. The rule parts are separated from each other by the SEMICOLON character. The rule parts are not ordered in any particular sequence. Individual rule parts MUST only be specified once.

The table below shows the supported rules and their usage.


FREQ	The FREQ rule part identifies the type of recurrence rule. This rule part MUST be specified in the recurrence rule. Valid values include SECONDLY, to specify repeating events based on an interval of a second or more; MINUTELY, to specify repeating events based on an interval of a minute or more; HOURLY, to specify repeating events based on an interval of an hour or more; DAILY, to specify repeating events based on an interval of a day or more; WEEKLY, to specify repeating events based on an interval of a week or more; MONTHLY, to specify repeating events based on an interval of a month or more; and YEARLY, to specify repeating events based on an interval of a year or more.
UNTIL	The UNTIL rule part defines a DATE (YYYYMMDD) or DATE-TIME (YYYYMMDDThhmmss) value that bounds the recurrence rule in an inclusive manner. If the value specified by UNTIL is synchronized with the specified recurrence, this DATE or DATE-TIME becomes the last instance of the recurrence. The value of the UNTIL rule part MUST have the same value type as the StartDate property. Furthermore, if the StartDate is specified as a date with local time, then the UNTIL rule part MUST also be specified as a date with local time. If the StartDate property is specified as a date with UTC time or a date with local time and time zone reference, then the UNTIL rule part MUST be specified as a date with UTC time. If not present, and the COUNT rule part is also not present, the "Rule" is considered to repeat forever.
COUNT	The COUNT rule part defines the number of occurrences at which to range-bound the recurrence. The StartDate property value always counts as the first occurrence.
INTERVAL	Positive integer representing at which intervals the recurrence rule repeats. The default value is "1", meaning every second for a SECONDLY rule, every minute for a MINUTELY rule, every hour for an HOURLY rule, etc. For example, within a DAILY rule, a value of "8" means every eight days.
BYSECOND	The BYSECOND rule part specifies a COMMA-separated list of seconds within a minute. Valid values are 0 to 60.
BYMINUTE	The BYMINUTE rule part specifies a COMMA-separated list of minutes within an hour. Valid values are 0 to 59.
BYHOUR	The BYHOUR rule part specifies a COMMA-separated list of hours of the day. Valid values are 0 to 23.
BYDAY	The BYDAY rule part specifies a COMMA-separated list of days of the week; SU indicates Sunday; MO indicates Monday; TU indicates Tuesday; WE indicates Wednesday; TH indicates Thursday; FR indicates Friday; and SA indicates Saturday. Each BYDAY value can also be preceded by a positive (+n) or negative (-n) integer. If present, this indicates the nth occurrence of a specific day within the MONTHLY or YEARLY Rule.
BYMONTHDAY	The BYMONTHDAY rule part specifies a COMMA-separated list of days of the month. Valid values are 1 to 31 or -31 to -1. For example, -10 represents the tenth to the last day of the month. The BYMONTHDAY rule part MUST NOT be specified when the FREQ rule part is set to WEEKLY.
BYYEARDAY	The BYYEARDAY rule part specifies a COMMA-separated list of days of the year. Valid values are 1 to 366 or -366 to -1. For example, -1 represents the last day of the year (December 31st) and -306 represents the 306th to the last day of the year (March 1st). The BYYEARDAY rule part MUST NOT be specified when the FREQ rule part is set to DAILY, WEEKLY, or MONTHLY.
BYWEEKNO	The BYWEEKNO rule part specifies a COMMA-separated list of ordinals specifying weeks of the year. Valid values are 1 to 53 or -53 to -1. This corresponds to weeks according to week numbering as defined in ISO.8601.2004. A week is defined as a seven day period, starting on the day of the week defined to be the week start (see WKST). Week number one of the calendar year is the first week that contains at least four (4) days in that calendar year. This rule part MUST NOT be used when the FREQ rule part is set to anything other than YEARLY. For example, 3 represents the third week of the year.
BYMONTH	The BYMONTH rule part specifies a COMMA-separated list of months of the year. Valid values are 1 to 12.
WKST	Specifies the day on which the workweek starts. Valid values are MO, TU, WE, TH, FR, SA, and SU. This is significant when a WEEKLY Rule has an interval greater than 1, and a BYDAY rule part is specified. This is also significant when in a YEARLY Rule when a BYWEEKNO rule part is specified. The default value is MO.
BYSETPOS	The BYSETPOS rule part specifies a COMMA-separated list of values that corresponds to the nth occurrence within the set of recurrence instances specified by the rule. BYSETPOS operates on a set of recurrence instances in one interval of the recurrence rule. For example, in a WEEKLY rule, the interval would be one week A set of recurrence instances starts at the beginning of the interval defined by the FREQ rule part. Valid values are 1 to 366 or -366 to -1. It MUST only be used in conjunction with another BYxxx rule part. For example "the last work day of the month" could be represented as: FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1. Each BYSETPOS value can include a positive (+n) or negative (-n) integer. If present, this indicates the nth occurrence of the specific occurrence within the set of occurrences specified by the rule.

Note: The BYSECOND, BYMINUTE and BYHOUR rule parts MUST NOT be specified when the associated StartDate property is specified.

Information not contained in the Rule necessary to determine the various recurrence instance start time and dates are derived from the StartDate property. For example, "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the month or a time. This information would be the same as what is specified for the StartDate property.

BYxxx rule parts modify the recurrence in some manner. BYxxx rule parts for a period of time that is the same or greater than the frequency generally reduce or limit the number of occurrences of the recurrence generated. For example, "FREQ=DAILY;BYMONTH=1" reduces the number of recurrence instances from all days (if BYMONTH rule part is not present) to all days in January. BYxxx rule parts for a period of time less than the frequency generally increase or expand the number of occurrences of the recurrence. For example, "FREQ=YEARLY;BYMONTH=1,2" increases the number of days within the yearly recurrence set from 1 (if BYMONTH rule part is not present) to 2.

If multiple BYxxx rule parts are specified, then after evaluating the specified FREQ and INTERVAL rule parts, the BYxxx rule parts are applied to the current set of evaluated occurrences in the following order: BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY, BYHOUR, BYMINUTE, BYSECOND and BYSETPOS; then COUNT and UNTIL are evaluated.

RecurrenceId
String
Default Value: ""

Identifies a recurring event.

This field is used in conjunction with the CalDAV UID and Sequence properties to identify a specific instance of a recurring event, todo, or journal. The value of this field is the value of the CalDAV StartDate property of the original recurrence instance.

Rule
String
Default Value: ""

This field defines the recurrence rule for the event.

The table below shows the supported rules and their usage.


FREQ	The FREQ rule part identifies the type of recurrence rule. This rule part MUST be specified in the recurrence rule. Valid values include SECONDLY, to specify repeating events based on an interval of a second or more; MINUTELY, to specify repeating events based on an interval of a minute or more; HOURLY, to specify repeating events based on an interval of an hour or more; DAILY, to specify repeating events based on an interval of a day or more; WEEKLY, to specify repeating events based on an interval of a week or more; MONTHLY, to specify repeating events based on an interval of a month or more; and YEARLY, to specify repeating events based on an interval of a year or more.
UNTIL	The UNTIL rule part defines a DATE (YYYYMMDD) or DATE-TIME (YYYYMMDDThhmmss) value that bounds the recurrence rule in an inclusive manner. If the value specified by UNTIL is synchronized with the specified recurrence, this DATE or DATE-TIME becomes the last instance of the recurrence. The value of the UNTIL rule part MUST have the same value type as the StartDate property. Furthermore, if the StartDate is specified as a date with local time, then the UNTIL rule part MUST also be specified as a date with local time. If the StartDate property is specified as a date with UTC time or a date with local time and time zone reference, then the UNTIL rule part MUST be specified as a date with UTC time. If not present, and the COUNT rule part is also not present, the "Rule" is considered to repeat forever.
COUNT	The COUNT rule part defines the number of occurrences at which to range-bound the recurrence. The StartDate property value always counts as the first occurrence.
INTERVAL	Positive integer representing at which intervals the recurrence rule repeats. The default value is "1", meaning every second for a SECONDLY rule, every minute for a MINUTELY rule, every hour for an HOURLY rule, etc. For example, within a DAILY rule, a value of "8" means every eight days.
BYSECOND	The BYSECOND rule part specifies a COMMA-separated list of seconds within a minute. Valid values are 0 to 60.
BYMINUTE	The BYMINUTE rule part specifies a COMMA-separated list of minutes within an hour. Valid values are 0 to 59.
BYHOUR	The BYHOUR rule part specifies a COMMA-separated list of hours of the day. Valid values are 0 to 23.
BYDAY	The BYDAY rule part specifies a COMMA-separated list of days of the week; SU indicates Sunday; MO indicates Monday; TU indicates Tuesday; WE indicates Wednesday; TH indicates Thursday; FR indicates Friday; and SA indicates Saturday. Each BYDAY value can also be preceded by a positive (+n) or negative (-n) integer. If present, this indicates the nth occurrence of a specific day within the MONTHLY or YEARLY Rule.
BYMONTHDAY	The BYMONTHDAY rule part specifies a COMMA-separated list of days of the month. Valid values are 1 to 31 or -31 to -1. For example, -10 represents the tenth to the last day of the month. The BYMONTHDAY rule part MUST NOT be specified when the FREQ rule part is set to WEEKLY.
BYYEARDAY	The BYYEARDAY rule part specifies a COMMA-separated list of days of the year. Valid values are 1 to 366 or -366 to -1. For example, -1 represents the last day of the year (December 31st) and -306 represents the 306th to the last day of the year (March 1st). The BYYEARDAY rule part MUST NOT be specified when the FREQ rule part is set to DAILY, WEEKLY, or MONTHLY.
BYWEEKNO	The BYWEEKNO rule part specifies a COMMA-separated list of ordinals specifying weeks of the year. Valid values are 1 to 53 or -53 to -1. This corresponds to weeks according to week numbering as defined in ISO.8601.2004. A week is defined as a seven day period, starting on the day of the week defined to be the week start (see WKST). Week number one of the calendar year is the first week that contains at least four (4) days in that calendar year. This rule part MUST NOT be used when the FREQ rule part is set to anything other than YEARLY. For example, 3 represents the third week of the year.
BYMONTH	The BYMONTH rule part specifies a COMMA-separated list of months of the year. Valid values are 1 to 12.
WKST	Specifies the day on which the workweek starts. Valid values are MO, TU, WE, TH, FR, SA, and SU. This is significant when a WEEKLY Rule has an interval greater than 1, and a BYDAY rule part is specified. This is also significant when in a YEARLY Rule when a BYWEEKNO rule part is specified. The default value is MO.
BYSETPOS	The BYSETPOS rule part specifies a COMMA-separated list of values that corresponds to the nth occurrence within the set of recurrence instances specified by the rule. BYSETPOS operates on a set of recurrence instances in one interval of the recurrence rule. For example, in a WEEKLY rule, the interval would be one week A set of recurrence instances starts at the beginning of the interval defined by the FREQ rule part. Valid values are 1 to 366 or -366 to -1. It MUST only be used in conjunction with another BYxxx rule part. For example "the last work day of the month" could be represented as: FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1. Each BYSETPOS value can include a positive (+n) or negative (-n) integer. If present, this indicates the nth occurrence of the specific occurrence within the set of occurrences specified by the rule.

Note: The BYSECOND, BYMINUTE and BYHOUR rule parts MUST NOT be specified when the associated StartDate property is specified.

Constructors

public CalRecurrence();

CalReportFilter Type

Used to restrict the results of a Report returned from the CalDAV server.

Remarks

You can restrict results to only events within a specified time range (using StartDate and EndDate), to only recurring events within a specified time range (using RecurStart and RecurEnd), and to events with an alarm set to go off within a specified time range. (using AlarmStart and AlarmEnd). You can also restrict results to only those events which contain a specific Property (either by property name, or name and a specific value). The EventType field determines what kind of events are returned (events, todo lists, journal entries, or free/busy time).

Fields

AlarmEnd
String
Default Value: ""

Limits the events returned in the report to only those with an alarm set in the range specified by AlarmStart and AlarmEnd. The date/time format is "YYYYMMDDThhmmss", where "T" indicates the break between date and time. You may also append a 1-character alpha code for the timezone. For instance, "20100104T123456Z" indicates January 4th, 2010 at 12:34:56 PM UTC.

AlarmStart
String
Default Value: ""

CustomFilter
String
Default Value: ""

Allows the user to specify his own filter XML. This property must be properly-formed XML, and must be a supported CalDAV filter or the component throws an exception.

EndDate
String
Default Value: ""

Limits the events returned in the report to only those which occur in the time range specified by StartDate and EndDate. The date/time format is "YYYYMMDDThhmmss", where "T" indicates the break between date and time. You may also append a 1-character alpha code for the timezone. For instance, "20100104T123456Z" indicates January 4th, 2010 at 12:34:56 PM UTC.

EventType
int
Default Value: 0

Indicates the type of calendar object resources to return in a Report. Some calendar servers (Google in particular) do not support vtAll, so you must submit a report for each type of event you wish to retrieve a report on.

Property
String
Default Value: ""

Limits the events returned in a Report to only those which contain a matching property name and value. For instance, setting the Property filter to "ORGANIZER" will return only events that have an organizer specified. Setting the Property filter to "ORGANIZER=mailto:JohnSmith@example.com" will return only resources where "mailto:JohnSmith@example.com" is the specified organizer. Likewise, you can retrieve a report on a single event by setting the Property filter with the UID of the needed resource. For example: Property = "UID=DC6C50A017428C5216A2F1CD@example.com";.

You may add multiple properties to the filter by separating them with commas. For example: "ORGANIZER=mailto:JohnSmith@example.com, STATUS=CANCELLED".

For more advanced filtering, you may specify your own CustomFilter.

RecurEnd
String
Default Value: ""

Limits the recurring events returned in the report.

Use of the CalDAV limit-recurrence-set element causes the server to only return overridden recurrence components that overlap the time range specified by RecurStart and RecurEnd or that affect other instances that overlap the time range specified by StartDate and EndDate. The date/time format is "YYYYMMDDThhmmss", where "T" indicates the break between date and time. You may also append a 1-character alpha code for the timezone. For instance, "20100104T123456Z" indicates January 4th, 2010 at 12:34:56 PM UTC.

Note that the RecurEnd field cannot be used when ReturnCalendarData is False.

RecurStart
String
Default Value: ""

Limits the recurring events returned in the report.

Note that the RecurStart field cannot be used when ReturnCalendarData is False.

ReturnCalendarData
boolean
Default Value: True

Controls whether the contents of each calendar event is returned in the report.

If ReturnCalendarData is True (default), a report will contain the full contents of each event in the calendar. This can be a substantially large amount of data. However if ReturnCalendarData is False, the report returned will contain only URIs and ETags of each calendar event. You may compare the URIs against a cached list and retrieve any new URIs individually via the CalDAV.GetCalendarEvent method. If the ETag for a cached URI has changed, it means that the calendar event has changed, and needs to be retrieved.

Note that this filter is not compatible with the RecurStart and RecurEnd fields.

StartDate
String
Default Value: ""

UID
String
Default Value: ""

Limits the recurring events returned in the report to only those with the specified UID.

Constructors

public CalReportFilter();

CalTimezone Type

Specifies a time zone on a calendar collection.

Remarks

The CalDAV CalTimezone type is used to specify the time zone the server should rely on to resolve "date" values and "date with local time" values (i.e., floating time) to "date with UTC time" values. The server will require this information to determine if a calendar component scheduled with "date" values or "date with local time" values overlaps a time range specified in a GetCalendarReport. In the absence of this property, the server may rely on a time zone of its choosing.

Fields

DSTName
String
Default Value: ""

The customary name for the daylight-savings time zone. This could be used for displaying dates, and there is no restriction to the format. For instance, Eastern Daylight Time may be represented as "EDT", "Eastern Daylight Time (US & Canada)", or any other arbitrary representation.

The following example shows the CalTimezone set to Eastern time. CalDAV.Timezone.TimezoneId = "US-Eastern"; CalDAV.Timezone.URL = "http://zones.example.com/tz/America-New_York.ics" CalDAV.Timezone.StdName = "Eastern Standard Time (US & Canada)"; CalDAV.Timezone.StdStart = "20071104T020000"; CalDAV.Timezone.StdOffsetFrom = "-400"; CalDAV.Timezone.StdOffsetTo = "-500"; CalDAV.Timezone.StdRule = "FREQ=YEARLY;BYDAY=1SU;BYMONTH=11"; CalDAV.TimeZone.DSTName = "Eastern Daylight Time (US & Canada)"; CalDAV.TimeZone.DSTStart = "20070311T020000"; CalDAV.TimeZone.DSTOffsetFrom = "-500"; CalDAV.TimeZone.DSTOffsetTo = "-400"; CalDAV.TimeZone.DSTRule = "FREQ=YEARLY;BYDAY=2SU;BYMONTH=3";

DSTOffsetFrom
String
Default Value: ""

The UTC offset that is in use when the onset of this time zone observance begins. DSTOffsetFrom is combined with DSTStart to define the effective onset for the daylight-time time zone definition.

DSTStart, DSTOffsetFrom, and DSTOffsetTo are all required to specify the daylight-savings time zone.

DSTOffsetTo
String
Default Value: ""

The UTC offset for daylight savings time, when this observance is in use.

DSTStart, DSTOffsetFrom, and DSTOffsetTo are all required to specify the daylight-savings time zone.

DSTRule
String
Default Value: ""

This field defines the recurrence rule for the onset of this daylight savings time observance. Some specific requirements for the usage of DSTRule for this purpose include:


FREQ	Frequency of the time zone onset. (Almost always "YEARLY")
BYMONTH	The month of the time zone onset.
BYDAY	The day of the time zone onset. Formatted as a number and a two-character day. "BYDAY=3SU" means the 3rd Sunday of the month. "BYDAY=-1SU" is the last Sunday of the month.
UNTIL	If the observance is known to have an effective end date, the "UNTIL" recurrence rule parameter MUST be used to specify the last valid onset of this observance (i.e., the UNTIL DATE-TIME will be equal to the last instance generated by the recurrence pattern). It MUST be specified in UTC time.

Note that the DSTStart and DSTOffsetFrom fields must be used when generating the onset DATE-TIME values (instances) from the DSTRule

For instance, in the USA Eastern Daylight time before 2007 started on the first Sunday of April. In 2007 Daylight time was changed to begin on the 2nd Sunday in March. Therefore, the UNTIL option should indicate the LAST time this rule will be observed. (2am on April 2nd, 2006). Such a time zone declaration would look like this: CalDAV.time zone.DSTName = "EDT" CalDAV.time zone.DSTStart = "19870405T020000" CalDAV.time zone.DSTOffsetFrom = "-500" CalDAV.time zone.DSTOffsetTo = "-400" CalDAV.time zone.DSTRule = "FREQ=YEARLY;BYMONTH=4;BYDAY=1SU;UNTIL=20060402T070000Z"

DSTStart
String
Default Value: ""

The effective onset date and local time for the daylight-time time zone definition. The date and time MUST be specified as a date with a local time value in the format "YYYYMMDDThhmmss", where "T" indicates the break between date and time.

DSTStart, DSTOffsetFrom, and DSTOffsetTo are all required to specify the daylight-savings time zone.

LastModified
String
Default Value: ""

This optional field is a UTC value that specifies the date and time that this time zone definition was last updated.

StdName
String
Default Value: ""

The customary name for the standard time zone. This could be used for displaying dates, and there is no restriction to the format. For instance, Eastern Standard Time may be represented as "EST", "Eastern Standard Time (US & Canada)", or any other arbitrary representation.

StdOffsetFrom
String
Default Value: ""

The UTC offset that is in use when the onset of this time zone observance begins. StdOffsetFrom is combined with StdStart to define the effective onset for the standard-time time zone definition.

StdStart, StdOffsetFrom, and StdOffsetTo are all required to specify the standard-time time zone.

StdOffsetTo
String
Default Value: ""

The UTC offset for standard time, when this observance is in use.

StdStart, StdOffsetFrom, and StdOffsetTo are all required to specify the standard-time time zone.

StdRule
String
Default Value: ""

This field defines the recurrence rule for the onset of this standard time observance. Some specific requirements for the usage of DSTRule for this purpose include:


FREQ	Frequency of the time zone onset. (Almost always "YEARLY")
BYMONTH	The month of the time zone onset.
BYDAY	The day of the time zone onset. Formatted as a number and a two-character day. "BYDAY=3SU" means the 3rd Sunday of the month. "BYDAY=-1SU" is the last Sunday of the month.
UNTIL	If the observance is known to have an effective end date, the "UNTIL" recurrence rule parameter MUST be used to specify the last valid onset of this observance (i.e., the UNTIL DATE-TIME will be equal to the last instance generated by the recurrence pattern). It MUST be specified in UTC time.

Note that the StdStart and StdOffsetFrom fields must be used when generating the onset DATE-TIME values (instances) from the StdRule

For instance, in the USA Eastern Standard time before 2007 started on the last Sunday of October. In 2007 Standard time was changed to begin on the 1st Sunday in November. Therefore, the UNTIL option should indicate the LAST time this rule will be observed. (2am on October 29th, 2006). Such a time zone declaration would look like this: CalDAV.time zone.StdName = "EST" CalDAV.time zone.StdStart = "19671029T020000" CalDAV.time zone.StdOffsetFrom = "-400" CalDAV.time zone.StdOffsetTo = "-500" CalDAV.time zone.StdRule = "FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU;UNTIL=20061029T060000Z"

StdStart
String
Default Value: ""

The effective onset date and local time for the standard-time time zone definition. The date and time MUST be specified as a date with a local time value. in the format "YYYYMMDDThhmmss", where "T" indicates the break between date and time.

StdStart, StdOffsetFrom, and StdOffsetTo are all required to specify the standard-time time zone.

TimezoneId
String
Default Value: ""

This field specifies a text value that uniquely identifies this CalTimezone calendar component.

Note: This document does not define a naming convention for time zone identifiers. Implementers may want to use the naming conventions defined in existing time zone specifications such as the public-domain TZ database [TZDB].

This field is required. If it is not present, no time zone information will be generated inside the MakeCalendar request.

URL
String
Default Value: ""

Optionally points to a published time zone definition. If set, this field should refer to a resource that is accessible by anyone who might need to interpret the object. This should not normally be a "file" URL or other URL that is not widely accessible.

Constructors

public CalTimezone();

Certificate Type

This is the digital certificate being used.

Remarks

This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates.

Fields

EffectiveDate
String (read-only)
Default Value: ""

This is the date on which this certificate becomes valid. Before this date, it is not valid. The following example illustrates the format of an encoded date:

23-Jan-2000 15:00:00.

Encoded
String
Default Value: ""

This is the certificate (PEM/Base64 encoded). This field is used to assign a specific certificate. The Store and Subject fields also may be used to specify a certificate.

When Encoded is set, a search is initiated in the current Store for the private key of the certificate. If the key is found, Subject is updated to reflect the full subject of the selected certificate; otherwise, Subject is set to an empty string.

EncodedB
byte []
Default Value: ""

This is the certificate (PEM/Base64 encoded). This field is used to assign a specific certificate. The Store and Subject fields also may be used to specify a certificate.

ExpirationDate
String (read-only)
Default Value: ""

This is the date the certificate expires. After this date, the certificate will no longer be valid. The following example illustrates the format of an encoded date:

23-Jan-2001 15:00:00.

ExtendedKeyUsage
String
Default Value: ""

This is a comma-delimited list of extended key usage identifiers. These are the same as ASN.1 object identifiers (OIDs).

Fingerprint
String (read-only)
Default Value: ""

This is the hex-encoded, 16-byte MD5 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: bc:2a:72:af:fe:58:17:43:7a:5f:ba:5a:7c:90:f7:02

FingerprintSHA1
String (read-only)
Default Value: ""

This is the hex-encoded, 20-byte SHA-1 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: 30:7b:fa:38:65:83:ff:da:b4:4e:07:3f:17:b8:a4:ed:80:be:ff:84

FingerprintSHA256
String (read-only)
Default Value: ""

This is the hex-encoded, 32-byte SHA-256 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: 6a:80:5c:33:a9:43:ea:b0:96:12:8a:64:96:30:ef:4a:8a:96:86:ce:f4:c7:be:10:24:8e:2b:60:9e:f3:59:53

Issuer
String (read-only)
Default Value: ""

This is the issuer of the certificate. This field contains a string representation of the name of the issuing authority for the certificate.

KeyPassword
String
Default Value: ""

This is the password for the certificate's private key (if any).

Some certificate stores may individually protect certificates' private keys, separate from the standard protection offered by the StorePassword. KeyPassword. This field can be used to read such password-protected private keys.

Note: this property defaults to the value of StorePassword. To clear it, you must set the property to the empty string (""). It can be set at any time, but when the private key's password is different from the store's password, then it must be set before calling PrivateKey.

PrivateKey
String (read-only)
Default Value: ""

This is the private key of the certificate (if available). The key is provided as PEM/Base64-encoded data.

Note: The PrivateKey may be available but not exportable. In this case, PrivateKey returns an empty string.

PrivateKeyAvailable
boolean (read-only)
Default Value: False

This field shows whether a PrivateKey is available for the selected certificate. If PrivateKeyAvailable is True, the certificate may be used for authentication purposes (e.g., server authentication).

PrivateKeyContainer
String (read-only)
Default Value: ""

This is the name of the PrivateKey container for the certificate (if available). This functionality is available only on Windows platforms.

PublicKey
String (read-only)
Default Value: ""

This is the public key of the certificate. The key is provided as PEM/Base64-encoded data.

PublicKeyAlgorithm
String
Default Value: ""

This field contains the textual description of the certificate's public key algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_DH") or an object identifier (OID) string representing the algorithm.

PublicKeyLength
int (read-only)
Default Value: 0

This is the length of the certificate's public key (in bits). Common values are 512, 1024, and 2048.

SerialNumber
String (read-only)
Default Value: ""

This is the serial number of the certificate encoded as a string. The number is encoded as a series of hexadecimal digits, with each pair representing a byte of the serial number.

SignatureAlgorithm
String (read-only)
Default Value: ""

The field contains the text description of the certificate's signature algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_MD5RSA") or an object identifier (OID) string representing the algorithm.

Store
String
Default Value: "MY"

This is the name of the certificate store for the client certificate.

The StoreType field denotes the type of the certificate store specified by Store. If the store is password protected, specify the password in StorePassword.

Store is used in conjunction with the Subject field to specify client certificates. If Store has a value, and Subject or Encoded is set, a search for a certificate is initiated. Please see the Subject field for details.

Designations of certificate stores are platform dependent.

The following designations are the most common User and Machine certificate stores in Windows:


MY	A certificate store holding personal certificates with their associated private keys.
CA	Certifying authority certificates.
ROOT	Root certificates.

In Java, the certificate store normally is a file containing certificates and optional private keys.

When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).

StoreB
byte []
Default Value: "MY"

This is the name of the certificate store for the client certificate.

The StoreType field denotes the type of the certificate store specified by Store. If the store is password protected, specify the password in StorePassword.

Designations of certificate stores are platform dependent.

The following designations are the most common User and Machine certificate stores in Windows:


MY	A certificate store holding personal certificates with their associated private keys.
CA	Certifying authority certificates.
ROOT	Root certificates.

In Java, the certificate store normally is a file containing certificates and optional private keys.

StorePassword
String
Default Value: ""

If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.

StoreType
int
Default Value: 0

This is the type of certificate store for this certificate.

The component supports both public and private keys in a variety of formats. When the cstAuto value is used, the component will automatically determine the type. This field can take one of the following values:


0 (cstUser - default)	For Windows, this specifies that the certificate store is a certificate store owned by the current user. Note: This store type is not available in Java.
1 (cstMachine)	For Windows, this specifies that the certificate store is a machine store. Note: This store type is not available in Java.
2 (cstPFXFile)	The certificate store is the name of a PFX (PKCS#12) file containing certificates.
3 (cstPFXBlob)	The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format.
4 (cstJKSFile)	The certificate store is the name of a Java Key Store (JKS) file containing certificates. Note: This store type is only available in Java.
5 (cstJKSBlob)	The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format. Note: this store type is only available in Java.
6 (cstPEMKeyFile)	The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate.
7 (cstPEMKeyBlob)	The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate.
8 (cstPublicKeyFile)	The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate.
9 (cstPublicKeyBlob)	The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate.
10 (cstSSHPublicKeyBlob)	The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key.
11 (cstP7BFile)	The certificate store is the name of a PKCS#7 file containing certificates.
12 (cstP7BBlob)	The certificate store is a string (binary) representing a certificate store in PKCS#7 format.
13 (cstSSHPublicKeyFile)	The certificate store is the name of a file that contains an SSH-style public key.
14 (cstPPKFile)	The certificate store is the name of a file that contains a PPK (PuTTY Private Key).
15 (cstPPKBlob)	The certificate store is a string (binary) that contains a PPK (PuTTY Private Key).
16 (cstXMLFile)	The certificate store is the name of a file that contains a certificate in XML format.
17 (cstXMLBlob)	The certificate store is a string that contains a certificate in XML format.
18 (cstJWKFile)	The certificate store is the name of a file that contains a JWK (JSON Web Key).
19 (cstJWKBlob)	The certificate store is a string that contains a JWK (JSON Web Key).
21 (cstBCFKSFile)	The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store). Note: This store type is only available in Java and .NET.
22 (cstBCFKSBlob)	The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format. Note: This store type is only available in Java and .NET.
23 (cstPKCS11)	The certificate is present on a physical security key accessible via a PKCS#11 interface. To use a security key, the necessary data must first be collected using the CertMgr component. The ListStoreCertificates method may be called after setting CertStoreType to `cstPKCS11`, CertStorePassword to the PIN, and CertStore to the full path of the PKCS#11 DLL. The certificate information returned in the CertList event's `CertEncoded` parameter may be saved for later use. When using a certificate, pass the previously saved security key information as the Store and set StorePassword to the PIN. Code Example. SSH Authentication with Security Key: `certmgr.CertStoreType = CertStoreTypes.cstPKCS11; certmgr.OnCertList += (s, e) => { secKeyBlob = e.CertEncoded; }; certmgr.CertStore = @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll"; certmgr.CertStorePassword = "123456"; //PIN certmgr.ListStoreCertificates(); sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, secKeyBlob, "123456", "*"); sftp.SSHUser = "test"; sftp.SSHLogon("myhost", 22);`
99 (cstAuto)	The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically.

Subject
String
Default Value: ""

This is the subject of the certificate used for client authentication.

This field will be populated with the full subject of the loaded certificate. When loading a certificate the subject is used to locate the certificate in the store.

If an exact match is not found, the store is searched for subjects containing the value of the property.

If a match is still not found, the property is set to an empty string, and no certificate is selected.

The special value "*" picks a random certificate in the certificate store.

The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=support@nsoftware.com". Common fields and their meanings are as follows:


Field	Meaning
CN	Common Name. This is commonly a hostname like www.server.com.
O	Organization
OU	Organizational Unit
L	Locality
S	State
C	Country
E	Email Address

If a field value contains a comma, it must be quoted.

SubjectAltNames
String (read-only)
Default Value: ""

This field contains comma-separated lists of alternative subject names for the certificate.

ThumbprintMD5
String (read-only)
Default Value: ""

This field contains the MD5 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

ThumbprintSHA1
String (read-only)
Default Value: ""

This field contains the SHA-1 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

ThumbprintSHA256
String (read-only)
Default Value: ""

This field contains the SHA-256 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

Usage
String
Default Value: ""

This field contains the text description of UsageFlags.

This value will be of one or more of the following strings and will be separated by commas:

Digital Signatures
Key Authentication
Key Encryption
Data Encryption
Key Agreement
Certificate Signing
Key Signing

If the provider is OpenSSL, the value is a comma-separated list of X.509 certificate extension names.

UsageFlags
int
Default Value: 0

This field contains the flags that show intended use for the certificate. The value of UsageFlags is a combination of the following flags:


0x80	Digital Signatures
0x40	Key Authentication (Non-Repudiation)
0x20	Key Encryption
0x10	Data Encryption
0x08	Key Agreement
0x04	Certificate Signing
0x02	Key Signing

Please see the Usage field for a text representation of UsageFlags.

This functionality currently is not available when the provider is OpenSSL.

Version
String (read-only)
Default Value: ""

This field contains the certificate's version number. The possible values are the strings "V1", "V2", and "V3".

Constructors

public Certificate();

Creates a Certificate instance whose properties can be set. This is useful for use with CERTMGR when generating new certificates.

public Certificate( certificateFile);

Opens CertificateFile and reads out the contents as an X.509 public key.

public Certificate( certificateData);

Parses CertificateData as an X.509 public key.

public Certificate( certStoreType,  store,  storePassword,  subject);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store. After the store has been successfully opened, the component will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN).

public Certificate( certStoreType,  store,  storePassword,  subject,  configurationString);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store. ConfigurationString is a newline separated list of name-value pairs that may be used to modify the default behavior. Possible values include "PersistPFXKey", which shows whether or not the PFX key is persisted after performing operations with the private key. This correlates to the PKCS12_NO_PERSIST_KEY CryptoAPI option. The default value is True (the key is persisted). "Thumbprint" - an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load. When specified, this value is used to select the certificate in the store. This is applicable to cstUser, cstMachine, cstPublicKeyFile, and cstPFXFile store types. "UseInternalSecurityAPI" shows whether the platform (default) or the internal security API is used when performing certificate-related operations. After the store has been successfully opened, the component will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN).

public Certificate( certStoreType,  store,  storePassword,  encoded);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store. After the store has been successfully opened, the component will load Encoded as an X.509 certificate and search the opened store for a corresponding private key.

public Certificate( certStoreType,  storeBlob,  storePassword,  subject);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. StoreBlob is a string (binary- or Base64-encoded) containing the certificate data. StorePassword is the password used to protect the store. After the store has been successfully opened, the component will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN).

public Certificate( certStoreType,  storeBlob,  storePassword,  subject,  configurationString);

public Certificate( certStoreType,  storeBlob,  storePassword,  encoded);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a string (binary- or Base64-encoded) containing the certificate store. StorePassword is the password used to protect the store. After the store has been successfully opened, the component will load Encoded as an X.509 certificate and search the opened store for a corresponding private key.

Firewall Type

The firewall the component will connect through.

Remarks

When connecting through a firewall, this type is used to specify different properties of the firewall, such as the firewall Host and the FirewallType.

Fields

AutoDetect
boolean
Default Value: False

This field tells the component whether or not to automatically detect and use firewall system settings, if available.

Connection information will first be obtained from Java system properties, such as http.proxyHost and https.proxyHost. Java properties may be set in a variety of ways; please consult the Java documentation for information about how firewall and proxy values can be specified.

If no Java system properties define connection information, the component will inspect the Windows registry for connection information that may be present on the system (applicable only on Windows systems).

FirewallType
int
Default Value: 0

This field determines the type of firewall to connect through. The applicable values are as follows:


fwNone (0)	No firewall (default setting).
fwTunnel (1)	Connect through a tunneling proxy. Port is set to 80.
fwSOCKS4 (2)	Connect through a SOCKS4 Proxy. Port is set to 1080.
fwSOCKS5 (3)	Connect through a SOCKS5 Proxy. Port is set to 1080.
fwSOCKS4A (10)	Connect through a SOCKS4A Proxy. Port is set to 1080.

Host
String
Default Value: ""

This field contains the name or IP address of firewall (optional). If a Host is given, the requested connections will be authenticated through the specified firewall when connecting.

If this field is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, this field is set to the corresponding address. If the search is not successful, the component throws an exception.

Password
String
Default Value: ""

This field contains a password if authentication is to be used when connecting through the firewall. If Host is specified, the User and Password fields are used to connect and authenticate to the given firewall. If the authentication fails, the component throws an exception.

Port
int
Default Value: 0

This field contains the transmission control protocol (TCP) port for the firewall Host. See the description of the Host field for details.

Note: This field is set automatically when FirewallType is set to a valid value. See the description of the FirewallType field for details.

User
String
Default Value: ""

This field contains a user name if authentication is to be used connecting through a firewall. If the Host is specified, this field and Password fields are used to connect and authenticate to the given Firewall. If the authentication fails, the component throws an exception.

Constructors

public Firewall();

Header Type

This is an HTTP header as it is received from the server.

Remarks

When a header is received through a Header event, it is parsed into a Header type. This type contains a Field, and its corresponding Value.

Fields

Field
String
Default Value: ""

This field contains the name of the HTTP Header (this is the same case as it is delivered).

Value
String
Default Value: ""

This field contains the Header contents.

Constructors

public Header();

public Header( field,  value);

HTTPCookie Type

An HTTP cookie can be either sent to or received from the server.

Remarks

An HTTP cookie can store the cookies that are to be sent to the server. It also may store the cookies sent by the server.

Cookies that are to be sent to the server must have the Name and Value fields supplied before submitting the URL. When the SetCookie event is fired, however, all of the fields of an HTTPCookie are filled out accordingly.

Fields

Domain
String (read-only)
Default Value: ""

This is the domain of a received cookie. This field contains a domain name to limit the cookie to (if provided by the server). If the server does not provide a domain name, this field will contain an empty string. The convention in this case is to use the server name specified by URLServer as the cookie domain.

Expiration
String (read-only)
Default Value: ""

This field contains an expiration time for the cookie (if provided by the server). The time format used is "Weekday, DD-Mon-YY HH:MM:SS GMT". If the server does not provide an expiration time, this field will contain an empty string. The convention is to drop the cookie at the end of the session.

Name
String
Default Value: ""

This field, contains the name of the cookie.

This field, along with Value, stores the cookie that is to be sent to the server. The SetCookie event displays the cookies sent by the server and their properties.

Path
String (read-only)
Default Value: ""

This field contains a path name to limit the cookie to (if provided by the server). If the server does not provide a cookie path, the path field will be an empty string. The convention in this case is to use the path specified by URLPath as the cookie path.

Secure
boolean (read-only)
Default Value: False

This field contains the security flag of the received cookie. This field specifies whether the cookie is secure. If the value of this field is True, the cookie value must be submitted only through a secure (HTTPS) connection.

Value
String
Default Value: ""

This field contains the value of the cookie. A corresponding value is associated with the cookie specified by Name. This property holds that value.

The SetCookie event provides the cookies set by the server.

Constructors

public HTTPCookie();

public HTTPCookie( name,  value);

Proxy Type

The proxy the component will connect to.

Remarks

When connecting through a proxy, this type is used to specify different properties of the proxy, such as the Server and the AuthScheme.

Fields

AuthScheme
int
Default Value: 0

This field is used to tell the component which type of authorization to perform when connecting to the proxy. This is used only when the User and Password fields are set.

AuthScheme should be set to authNone (3) when no authentication is expected.

By default, AuthScheme is authBasic (0), and if the User and Password fields are set, the component will attempt basic authentication.

If AuthScheme is set to authDigest (1), digest authentication will be attempted instead.

If AuthScheme is set to authProprietary (2), then the authorization token will not be generated by the component. Look at the configuration file for the component being used to find more information about manually setting this token.

If AuthScheme is set to authNtlm (4), NTLM authentication will be used.

For security reasons, setting this field will clear the values of User and Password.

AutoDetect
boolean
Default Value: False

This field tells the component whether or not to automatically detect and use proxy system settings, if available. The default value is false.

Note: This setting is applicable only in Windows.

Password
String
Default Value: ""

This field contains a password if authentication is to be used for the proxy.

If AuthScheme is set to Basic Authentication, the User and Password are Base64 encoded and the proxy authentication token will be generated in the form Basic [encoded-user-password].

If AuthScheme is set to Digest Authentication, the User and Password fields are used to respond to the Digest Authentication challenge from the server.

If AuthScheme is set to NTLM Authentication, the User and Password fields are used to authenticate through NTLM negotiation.

Port
int
Default Value: 80

This field contains the Transmission Control Protocol (TCP) port for the proxy Server (default 80). See the description of the Server field for details.

Server
String
Default Value: ""

If a proxy Server is given, then the HTTP request is sent to the proxy instead of the server otherwise specified.

If the Server field is set to a domain name, a DNS request is initiated. Upon successful termination of the request, the Server field is set to the corresponding address. If the search is not successful, an error is returned.

SSL
int
Default Value: 0

This field determines when to use a Secure Sockets Layer (SSL) for the connection to the proxy. The applicable values are as follows:


psAutomatic (0)	Default setting. If the URL is an `https` URL, the component will use the `psTunnel` option. If the URL is an `http` URL, the component will use the `psNever` option.
psAlways (1)	The connection is always SSL enabled.
psNever (2)	The connection is not SSL enabled.
psTunnel (3)	The connection is made through a tunneling (HTTP) proxy.

User
String
Default Value: ""

This field contains a username if authentication is to be used for the proxy.

If AuthScheme is set to Basic Authentication, the User and Password fields are Base64 encoded and the proxy authentication token will be generated in the form Basic [encoded-user-password].

If AuthScheme is set to Digest Authentication, the User and Password fields are used to respond to the Digest Authentication challenge from the server.

If AuthScheme is set to NTLM Authentication, the User and Password fields are used to authenticate through NTLM negotiation.

Constructors

public Proxy();

public Proxy( server,  port);

public Proxy( server,  port,  user,  password);

Config Settings (Caldav Component)

The component accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.

CalDAV Config Settings

AuthScheme: The authentication scheme to use for server authorization.

This setting is used to support non-standard CalDAV server authentication. The following values are supported:


0	Basic
1	Digest
2	Proprietary
3	None
4	NTLM

Use the AuthScheme setting to tell the component which type of authorization to perform when the User and Password properties are set. By default, CalDav servers use Basic authentication, and if the User and Password properties are set, the component will attempt basic authentication. Digest, NTLM, and Negotiate authentication are also available to support custom CalDAV server implementations.

Note that if the AuthScheme is set to Proprietary (2) then the authorization token must be supplied through Authorization setting.

For security purposes, changing the value of this property will cause the component to clear the values of User, Password and Authorization.

BuildEvent: Builds the current event for a multi-event calendar entry.

Calling this setting signals the component to build the current event for a multi-event calendar entry (typically a recurring event with one or more 'exception' events).

Note: this setting is used in conjunction with StartCalendar and EndCalendar.

EndCalendar: Signifies the end of a multi-event calendar entry.

This setting signifies the end of a multi-event calendar entry (typically a recurring event with one or more 'exception' events). Calling this setting returns the data for the calendar, which can then be imported using the ImportICS method.

Note: this setting is used in conjunction with BuildEvent and StartCalendar.

ExpandRecurringEvents: Instructs the component to return all instances of a recurring event within a timeframe.

When false (default), the CalDAV server will return only a single response for each recurring event along with the recurrence rules. If this configuration option is set to true the CalDAV server will return a response for each instance of a recurring event during a given time interval. The ReportFilter.RecurStart and ReportFilter.RecurEnd fields must also be set to use this functionality. Please see the example code below: calDAV.ReportFilter.StartDate = "20120130T000000Z"; calDAV.ReportFilter.EndDate = "20120203T235959Z"; calDAV.ReportFilter.RecurStart = calDAV.ReportFilter.StartDate; calDAV.ReportFilter.RecurEnd = calDAV.ReportFilter.EndDate; calDAV.Config("ExpandRecurringEvents=true"); calDAV.ReportFilter.ReturnCalendarData = true; calDAV.ReportFilter.EventType = VEventTypes.vtAll; calDAV.GetCalendarReport("http://www.some-url.com/caldav.php/events");

ListCalendars: Instructs the component list all the calendars for the current user.

To initiate the listing of the calendars, the configuration setting needs to be set to the calendar URI for the server. Then using the calDAV URI, the component will first initiate a PROPFIND to get the current-user-principle. Once the current user has been found, it will then use that information to initiate a second PROPFIND to get calendar-home-set for thte user. This calendar-home-set can then be used by the component to make a final PROPFIND to get the full list of calendars for the user. Once the response has been parsed, the component will set the ListCalendarsResultCount, ListCalendarsResultURL[i] and, ListCalendarsResultDisplayName[i] configuration settings. calDAV.Config("ListCalendars=https://apidata.googleusercontent.com/caldav/v2"); string count = calDAV.Config("ListCalendarsResultCount"); for (int i = 0; i < int.Parse(count); i++) { string url = calDAV.Config("ListCalendarsResultURL[" + i + "]"); string displayName = calDAV.Config("ListCalendarsResultDisplayName[" + i + "]"); ... // TODO: }

ListCalendarsResultCount: Provides the number of calendars found when listing.

The number of calendars found when ListCalendars is used to get a list of calendars for the current user.

ListCalendarsResultDisplayName[i]: Provides the name of a listed calendar.

This setting can be queried to get the name of a specific calendar. See ListCalendars for more information.

ListCalendarsResultURL[i]: Provides the URL of a listed calendar.

This setting can be queried to get the URL of a specific calendar. See ListCalendars for more information.

ProductId: Specifies the identifier for the product that created the iCalendar object.

The vendor of the implementation should assure that this is a globally unique identifier.

This setting should not be used to alter the interpretation of a calendar resource. For example, it is not to be used to further the understanding of non-standard properties.

This setting is required to have a value when creating a new calendar collection resource via the CreateCalendar method. For all others it is optional.

RecurrenceExceptionDatesAttrs: Specifies the attributes for the exception dates of a recurring event.

This setting specifies the attributes for the exception dates of a recurring event. The setting should be populated with a COMMA-separated list of one or more attributes, where each attribute is applied to the corresponding date listed in the ExceptionDates field of the Recurrence property.

The table below shows some examples of supported values.


VALUE=DATE,VALUE=DATE	Attributes for the FIRST and SECOND exception dates.
VALUE=DATE,	Attribute for the FIRST exception date.
,VALUE=DATE	Attribute for the SECOND exception date.

StartCalendar: Signifies the beginning of a multi-event calendar entry.

This setting signifies the beginning of a multi-event calendar entry (typically a recurring event with one or more 'exception' events).

Note: this setting is used in conjunction with BuildEvent and EndCalendar.

WebDAV Config Settings

EncodeURL: If set to true the URL will be encoded by the component.

The default value is false. If set to true the URL passed to the component will be URL encoded.

IsDir[i]: Whether or not the resource at the specified index is a directory.

After calling ListDirectory, this config can be queried to determine whether or not the resource at index i is a directory (collection): webdav.ListDirectory("https://localhost/DAV/"); bool isDir = Convert.ToBoolean(webdav.Config("IsDir[0]"));

An exception will be thrown if an invalid index is specified.

MaxResources: Instructs component to save the amount of resources specified that are returned by the server after a ListDirectory call has been made.

This config should be set when the Resources collection will be populated after a call to ListDirectory. This value represents the number of resources that are to be saved in the collection.

To save all items to the collection, set this configuration setting to -1. If no items are wanted, set this to 0, which will not save any items to the collection. The default for this configuration setting is -1, so all items will be included in the collection.

QueryPropertyNames: Instructs component explicitly request certain properties when calling ListDirectory.

Set this to a comma-delimited list of property names that should come back from the server when calling ListDirectory. Any returned properties will be available in Properties.

Normally servers will return all properties for a resource, but in some cases it is costly to get certain properties. It is perfectly valid in the RFC to not return certain properties the server deems are too costly to return. In these situations specific properties can be explicitly requested from the server using this configuration setting.

dav.OnDirList += (obj, ev) => Debug.WriteLine("The creationdate for " + ev.DisplayName + " is " + dav.GetProperty("creationdate")); dav.Config("QueryPropertyNames=creationdate"); dav.ListDirectory("http://webdav-server.com/DAV/");

HTTP Config Settings

AcceptEncoding: Used to tell the server which types of content encodings the client supports.

When AllowHTTPCompression is True, the component adds an Accept-Encoding header to the request being sent to the server. By default, this header's value is "gzip, deflate". This configuration setting allows you to change the value of the Accept-Encoding header. Note: The component only supports gzip and deflate decompression algorithms.

AllowHTTPCompression: This property enables HTTP compression for receiving data.

This configuration setting enables HTTP compression for receiving data. When set to True (default), the component will accept compressed data. It then will uncompress the data it has received. The component will handle data compressed by both gzip and deflate compression algorithms.

When True, the component adds an Accept-Encoding header to the outgoing request. The value for this header can be controlled by the AcceptEncoding configuration setting. The default value for this header is "gzip, deflate".

The default value is True.

AllowHTTPFallback: Whether HTTP/2 connections are permitted to fallback to HTTP/1.1.

This configuration setting controls whether HTTP/2 connections are permitted to fall back to HTTP/1.1 when the server does not support HTTP/2. This setting is applicable only when HTTPVersion is set to "2.0".

If set to True (default), the component will automatically use HTTP/1.1 if the server does not support HTTP/2. If set to False, the component throws an exception if the server does not support HTTP/2.

The default value is True.

AllowNTLMFallback: Whether to allow fallback from Negotiate to NTLM when authenticating.

This configuration setting applies only when AuthScheme is set to Negotiate. If set to True, the component will automatically use New Technology LAN Manager (NTLM) if the server does not support Negotiate authentication. Note: The server must indicate that it supports NTLM authentication through the WWW-Authenticate header for the fallback from Negotiate to NTLM to take place. The default value is False.

Append: Whether to append data to LocalFile.

This configuration setting determines whether data will be appended when writing to LocalFile. When set to True, downloaded data will be appended to LocalFile. This may be used in conjunction with Range to resume a failed download. This is applicable only when LocalFile is set. The default value is False.

Authorization: The Authorization string to be sent to the server.

If the Authorization property contains a nonempty string, an Authorization HTTP request header is added to the request. This header conveys Authorization information to the server.

This property is provided so that the HTTP component can be extended with other security schemes in addition to the authorization schemes already implemented by the component.

BytesTransferred: Contains the number of bytes transferred in the response data.

This configuration setting returns the raw number of bytes from the HTTP response data, before the component processes the data, whether it is chunked or compressed. This returns the same value as the Transfer event, by BytesTransferred.

ChunkSize: Specifies the chunk size in bytes when using chunked encoding.

This is applicable only when UseChunkedEncoding is True. This setting specifies the chunk size in bytes to be used when posting data. The default value is 16384.

CompressHTTPRequest: Set to true to compress the body of a PUT or POST request.

If set to True, the body of a PUT or POST request will be compressed into gzip format before sending the request. The "Content-Encoding" header is also added to the outgoing request.

The default value is False.

EncodeURL: If set to True the URL will be encoded by the component.

If set to True, the URL passed to the component will be URL encoded. The default value is False.

FollowRedirects: Determines what happens when the server issues a redirect.

This option determines what happens when the server issues a redirect. Normally, the component returns an error if the server responds with an "Object Moved" message. If this property is set to 1 (always), the new URL for the object is retrieved automatically every time.

If this property is set to 2 (Same Scheme), the new URL is retrieved automatically only if the URL Scheme is the same; otherwise, the component throws an exception.

Note: Following the HTTP specification, unless this option is set to 1 (Always), automatic redirects will be performed only for GET or HEAD requests. Other methods potentially could change the conditions of the initial request and create security vulnerabilities.

Furthermore, if either the new URL server or port are different from the existing one, User and Password are also reset to empty, unless this property is set to 1 (Always), in which case the same credentials are used to connect to the new server.

The default value is 0 (Never). In this case, redirects are never followed, and the component throws an exception instead.

Following are the valid options:

0 - Never
1 - Always
2 - Same Scheme

GetOn302Redirect: If set to True the component will perform a GET on the new location.

The default value is False. If set to True, the component will perform a GET on the new location. Otherwise, it will use the same HTTP method again.

HTTP2HeadersWithoutIndexing: HTTP2 headers that should not update the dynamic header table with incremental indexing.

HTTP/2 servers maintain a dynamic table of headers and values seen over the course of a connection. Typically, these headers are inserted into the table through incremental indexing (also known as HPACK, defined in RFC 7541). To tell the component not to use incremental indexing for certain headers, and thus not update the dynamic table, set this configuration option to a comma-delimited list of the header names.

HTTPVersion: The version of HTTP used by the component.

This property specifies the HTTP version used by the component. Possible values are as follows:

"1.0"
"1.1" (default)
"2.0"
"3.0"

When using HTTP/2 ("2.0"), additional restrictions apply. Please see the following notes for details.

HTTP/2 Notes

When using HTTP/2, a secure Secure Sockets Layer/Transport Layer Security (TLS/SSL) connection is required. Attempting to use a plaintext URL with HTTP/2 will result in an error.

If the server does not support HTTP/2, the component will automatically use HTTP/1.1 instead. This is done to provide compatibility without the need for any additional settings. To see which version was used, check NegotiatedHTTPVersion after calling a method. The AllowHTTPFallback setting controls whether this behavior is allowed (default) or disallowed.

HTTP/2 is supported on all platforms. The component will use the internal security implementation in all cases when connecting.

HTTP/3 Notes

HTTP/3 is supported only in .NET and Java.

When using HTTP/3, a secure (TLS/SSL) connection is required. Attempting to use a plaintext URL with HTTP/3 will result in an error.

IfModifiedSince: A date determining the maximum age of the desired document.

If this setting contains a nonempty string, an If-Modified-Since HTTP header is added to the request. The value of this header is used to make the HTTP request conditional: if the requested documented has not been modified since the time specified in the field, a copy of the document will not be returned from the server; instead, a 304 (not modified) response will be returned by the server and the component throws an exception

The format of the date value for IfModifiedSince is detailed in the HTTP specs. For example: Sat, 29 Oct 2017 19:43:31 GMT.

KeepAlive: Determines whether the HTTP connection is closed after completion of the request.

If true, the component will not send the Connection: Close header. The absence of the Connection header indicates to the server that HTTP persistent connections should be used if supported. Note: Not all servers support persistent connections. If false, the connection will be closed immediately after the server response is received.

The default value for KeepAlive is false.

KerberosSPN: The Service Principal Name for the Kerberos Domain Controller.

If the Service Principal Name on the Kerberos Domain Controller is not the same as the URL that you are authenticating to, the Service Principal Name should be set here.

LogLevel: The level of detail that is logged.

This configuration setting controls the level of detail that is logged through the Log event. Possible values are as follows:


0 (None)	No events are logged.
1 (Info - default)	Informational events are logged.
2 (Verbose)	Detailed data are logged.
3 (Debug)	Debug data are logged.

The value 1 (Info) logs basic information, including the URL, HTTP version, and status details.

The value 2 (Verbose) logs additional information about the request and response.

The value 3 (Debug) logs the headers and body for both the request and response, as well as additional debug information (if any).

MaxHeaders: Instructs component to save the amount of headers specified that are returned by the server after a Header event has been fired.

This configuration setting should be set when the TransferredHeaders collection is to be populated when a Header event has been fired. This value represents the number of headers that are to be saved in the collection.

MaxHTTPCookies: Instructs component to save the amount of cookies specified that are returned by the server when a SetCookie event is fired.

This configuration setting should be set when populating the Cookies collection as a result of an HTTP request. This value represents the number of cookies that are to be saved in the collection.

MaxRedirectAttempts: Limits the number of redirects that are followed in a request.

When FollowRedirects is set to any value other than frNever, the component will follow redirects until this maximum number of redirect attempts are made. The default value is 20.

NegotiatedHTTPVersion: The negotiated HTTP version.

This configuration setting may be queried after the request is complete to indicate the HTTP version used. When HTTPVersion is set to "2.0" (if the server does not support "2.0"), then the component will fall back to using "1.1" automatically. This setting will indicate which version was used.

OtherHeaders: Other headers as determined by the user (optional).

This configuration setting can be set to a string of headers to be appended to the HTTP request headers.

The headers must follow the format "header: value" as described in the HTTP specifications. Header lines should be separated by CRLF ("\r\n") .

Use this configuration setting with caution. If this configuration setting contains invalid headers, HTTP requests may fail.

This configuration setting is useful for extending the functionality of the component beyond what is provided.

ProxyAuthorization: The authorization string to be sent to the proxy server.

This is similar to the Authorization configuration setting, but is used for proxy authorization. If this configuration setting contains a nonempty string, a Proxy-Authorization HTTP request header is added to the request. This header conveys proxy Authorization information to the server. If User and Password are specified, this value is calculated using the algorithm specified by AuthScheme.

ProxyAuthScheme: The authorization scheme to be used for the proxy.