directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-711) Propagate the errors to the client if we get a DecoderException (was DIRSERVER-634)
Date Tue, 29 Aug 2006 23:54:23 GMT
    [ http://issues.apache.org/jira/browse/DIRSERVER-711?page=comments#action_12431415 ] 
            
Emmanuel Lecharny commented on DIRSERVER-711:
---------------------------------------------

57% done. This is 38/66 (reevaluation of the number of case is being done).

Here is the status for current done cases :

UnbindRequest (1) :
-------------------
125 : PROTOCOL_ERROR : DONE : Tested

LdapControl (4) :
-----------------
186 : PROTOCOL_ERROR : DONE : Tested
195 : PROTOCOL_ERROR : DONE : Tested
214 : PROTOCOL_ERROR : DONE : Tested
275 : PROTOCOL_ERROR : DONE : Tested

LdapMessage (3) :
-----------------
103 : PROTOCOL_ERROR : DONE : Tested
148 : PROTOCOL_ERROR : DONE : Tested
170 : PROTOCOL_ERROR : DONE : Tested


AbandonRequest (2) :
--------------------
118 : Null messageId : PROTOCOL_ERROR : DONE : Tested
149 : Bad messageId : PROTOCOL_ERROR : DONE : Tested

AddRequest (5) :
----------------
117 : Empty addRequest : PROTOCOL_ERROR : DONE : Tested
160 : The entry is null : NAMING_VIOLATION : DONE : Tested
179 : Invalid entry : INVALID_DN_SYNTAX : DONE : Tested
270 : Empty attribute : INVALID_ATTRIBUTE_SYNTAX : DONE : Tested
284 : Invalid attribute : NAMING_EXCEPTION : DONE : not testable

BindRequest (5) :
-----------------
135 : Empty request : PROTOCOL_ERROR : DONE : Tested
183 : Invalid Ldap version : PROTOCOL_ERROR : DONE : Tested
236 : Bad DN : INVALID_DN_SYNTAX : DONE : Tested
364 : Empty SASL : INVALID_CREDENTIALS : DONE : Tested
437 : Bad mechanism : INAPPROPRIATE_AUTHENTICATION : DONE : not testable

CompareRequest (4) :
--------------------
145 : Empty entry : PROTOCOL_ERROR : DONE : Tested
163 : Bad entry : INVALID_DN_SYNTAX : DONE : Tested
228 : Empty attributeDesc : INVALID_ATTRIBUTE_SYNTAX : DONE : Tested
241 : Bad attributeDesc : NAMING_VIOLATION : DONE : not testable

DelRequest (2) :
----------------
114 : Empty DN : PROTOCOL_ERROR : DONE : Tested
132 : Bad DN : INVALID_DN_SYNTAX : DONE : Tested

ExtendedRequest (2) :
---------------------
135 : Empty request name : PROTOCOL_ERROR : DONE : Tested
158 : Invalid OID : PROTOCOL_ERROR : DONE : Tested

ModifyRequest (4) :
-------------------
163 : Bad object : INVALID_DN_SYNTAX  : DONE : Tested
280 : Bad operation : PROTOCOL_ERROR : DONE : Tested
356 : Empty type : INVALID_ATTRIBUTE_SYNTAX : DONE : Tested
371 : Bad type : INVALID_ATTRIBUTE_SYNTAX : DONE : Not testable

ModifyDNRequest (6) :
---------------------
147 : Empty entry : PROTOCOL_ERROR : DONE : Tested
165 : Bad entry : INVALID_DN_SYNTAX : DONE : Tested
221 : Empty newRDN : PROTOCOL_ERROR : DONE : Tested : <---- Is this the correct error ?
Or should we produce a INVALID_DN_SYNTAX
240 : Bad newRDN : INVALID_DN_SYNTAX : DONE : Tested
300 : Invalid oldRDN : PROTOCOL_ERROR : DONE : tested
389 : Invalid newSuperior : INVALID_DN_SYNTAX : DONE : Tested


> Propagate the errors to the client if we get a DecoderException (was DIRSERVER-634)
> -----------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-711
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-711
>             Project: Directory ApacheDS
>          Issue Type: Bug
>            Reporter: Emmanuel Lecharny
>         Assigned To: Emmanuel Lecharny
>
> In codec grammars, when we have a decoderException, we should generate the correct LdapMessage
response so the client can get the correct error instead of a protocol error.

-- 
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

        

Mime
View raw message