You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2006/10/02 16:00:23 UTC
[jira] Closed: (DIRSERVER-281) Extended operation for Notice of
DIsconnect (Unsolicited Notification)
[ http://issues.apache.org/jira/browse/DIRSERVER-281?page=all ]
Alex Karasulu closed DIRSERVER-281.
-----------------------------------
fixed and confirmed
> Extended operation for Notice of DIsconnect (Unsolicited Notification)
> ----------------------------------------------------------------------
>
> Key: DIRSERVER-281
> URL: http://issues.apache.org/jira/browse/DIRSERVER-281
> Project: Directory ApacheDS
> Issue Type: New Feature
> Affects Versions: pre-1.0
> Reporter: Alex Karasulu
> Assigned To: Alex Karasulu
> Fix For: 1.0-RC1
>
>
> From RFC 2251 here
> Section 4.1.1 (Small snippent on sending NoD)
> If the server receives a PDU from the client in which the LDAPMessage
> SEQUENCE tag cannot be recognized, the messageID cannot be parsed,
> the tag of the protocolOp is not recognized as a request, or the
> encoding structures or lengths of data fields are found to be
> incorrect, then the server MUST return the notice of disconnection
> described in section 4.4.1, with resultCode protocolError, and
> immediately close the connection. In other cases that the server
> cannot parse the request received by the client, the server MUST
> return an appropriate response to the request, with the resultCode
> set to protocolError.
> 4.4.1. Notice of Disconnection
> This notification may be used by the server to advise the client that
> the server is about to close the connection due to an error
> condition. Note that this notification is NOT a response to an
> unbind requested by the client: the server MUST follow the procedures
> of section 4.3. This notification is intended to assist clients in
> distinguishing between an error condition and a transient network
> failure. As with a connection close due to network failure, the
> client MUST NOT assume that any outstanding requests which modified
> the directory have succeeded or failed.
> The responseName is 1.3.6.1.4.1.1466.20036, the response field is
> absent, and the resultCode is used to indicate the reason for the
> disconnection.
> The following resultCode values are to be used in this notification:
> - protocolError: The server has received data from the client in
> which
> the LDAPMessage structure could not be parsed.
> - strongAuthRequired: The server has detected that an established
> underlying security association protecting communication between
> the client and server has unexpectedly failed or been compromised.
> - unavailable: This server will stop accepting new connections and
> operations on all existing connections, and be unavailable for an
> extended period of time. The client may make use of an alternative
> server.
> After sending this notice, the server MUST close the connection.
> After receiving this notice, the client MUST NOT transmit any further
> on the connection, and may abruptly close the connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira