Click or drag to resize

ErrorDetails Structure

IT Hit WebDAV Classes Reference
Describes detail that can be passed to DavException.

Namespace:  ITHit.WebDAV.Server
Assembly:  ITHit.WebDAV.Server (in ITHit.WebDAV.Server.dll) Version: 9.1.5460-Beta
public struct ErrorDetails : IEquatable<ErrorDetails>

The ErrorDetails type exposes the following members.

Public methodErrorDetails
Initializes a new instance of the ErrorDetails struct.
Public propertyName
Gets element name.
Public propertyNamespace
Gets element namespace.
Public methodEquals(Object)
Indicates whether this instance and a specified object are equal.
(Overrides ValueTypeEquals(Object).)
Public methodEquals(ErrorDetails)
Indicates whether the current object is equal to another object of the same type.
Public methodGetHashCode
Returns the hash code for this instance.
(Overrides ValueTypeGetHashCode.)
Public methodGetType
Gets the Type of the current instance.
(Inherited from Object.)
Public methodToString
Returns the fully qualified type name of this instance.
(Inherited from ValueType.)
Public operatorStatic memberEquality
Equality operator.
Public operatorStatic memberInequality
Inequality operator.
Public fieldStatic memberCANNOT_COPY_HISTORY
If the request-URL identifies a version history, the request MUST fail. In order to create another version history whose versions have the same content and dead properties, the appropriate sequence of VERSION-CONTROL, CHECKOUT, PUT, PROPPATCH, and CHECKIN requests must be made
The client attempted to set a protected property in a PROPPATCH (such as DAV:getetag).
Public fieldStatic memberCANNOT_MODIFY_VERSION
If the request-URL identifies a version, the request MUST fail.
If the request-URL identifies a resource with a DAV:checked-in property, the request MUST fail unless DAV:auto-version semantics will automatically check out the resource.
If the request attempts to modify a dead property, same semantics as PUT
Public fieldStatic memberCANNOT_RENAME_HISTORY
If the request-URL identifies a version history, the request MUST fail.
Public fieldStatic memberCANNOT_RENAME_VERSION
If the request-URL identifies a version, the request MUST fail.
A request may include a Lock-Token header to identify a lock for the UNLOCK method. However, if the Request-URI does not fall within the scope of the lock identified by the token, the server SHOULD use this error. The lock may have a scope that does not include the Request-URI, or the lock could have disappeared, or the token may be invalid.
Public fieldStatic memberLOCK_TOKEN_SUBMITTED
The request could not succeed because a lock token should have been submitted. This element, if present, MUST contain at least one URL of a locked resource that prevented the request. In cases of MOVE, COPY, and DELETE where collection locks are involved, it can be difficult for the client to find out which locked resource made the request fail -- but the server is only responsible for returning one such locked resource. The server MAY return every locked resource that prevented the request from succeeding if it knows them all.
Public fieldStatic memberMUST_BE_CHECKED_IN
If a version-controlled resource is being checked out, it MUST have a DAV:checked-in property
Public fieldStatic memberMUST_BE_CHECKED_OUT
If a version-controlled resource is being checked out, it MUST have a DAV:checked-out property
The request-URL MUST identify a version-controlled resource with a DAV:checked-out property.
Public fieldStatic memberNO_CONFLICTING_LOCK
A LOCK request failed due the presence of an already existing conflicting lock. Note that a lock can be in conflict although the resource to which the request was directed is only indirectly locked. In this case, the precondition code can be used to inform the client about the resource that is the root of the conflicting lock, avoiding a separate lookup of the "lockdiscovery" property.
Public fieldStatic memberNO_EXTERNAL_ENTITIES
If the server rejects a client request because the request body contains an external entity, the server SHOULD use this error.
Public fieldStatic memberNO_VERSION_DELETE
A server MAY fail an attempt to DELETE a version.
The number of matching principals must fall within server-specific, predefined limits. For example, this condition might be triggered if a search specification would cause the return of an extremely large number of responses.
Public fieldStatic memberPRESERVED_LIVE_PROPERTIES
The server received an otherwise-valid MOVE or COPY request, but cannot maintain the live properties with the same behavior at the destination. It may be that the server only supports some live properties in some parts of the repository, or simply has an internal error.
Public fieldStatic memberPROPFIND_FINITE_DEPTH
This server does not allow infinite-depth PROPFIND requests on collections.
Public fieldStatic memberSUPPORTED_LIVE_PROPERTY
If the request attempts to access a property defined by this document, the semantics of that property MUST be supported by the server.
Public fieldStatic memberSUPPORTED_REPORT
The specified report MUST be supported by the resource identified by the request-URL.
Public fieldStatic memberVERSION_HISTORY_IS_TREE
If the request-URL identifies a checked-out version-controlled resource that will be automatically checked in when the lock is removed, then the versions identified by the DAV:predecessor-set of the checked-out resource MUST be descendants of the root version of the version history for the DAV:checked-out version.
See Also