You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by di...@incubator.apache.org on 2004/08/23 00:58:20 UTC

[jira] Closed: (DIRSNICKERS-84) Enable both determinate and inderminate length encodings

Message:

   The following issue has been closed.

   Resolver: Alex Karasulu
       Date: Sun, 22 Aug 2004 3:58 PM

Indeterminate length encodings are illegal in LDAP according to section 5.1 of RFC 2251.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSNICKERS-84

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSNICKERS-84
    Summary: Enable both determinate and inderminate length encodings
       Type: Task

     Status: Closed
   Priority: Major
 Resolution: WON'T FIX

    Project: Directory Snickers
 Components: 
             LDAP Provider

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Sun, 15 Aug 2004 5:00 PM
    Updated: Sun, 22 Aug 2004 3:58 PM

Description:
Basically there seems to be a problem using the indeterminate length form for encoding LDAP messages.  For some reason several clients seem to reject this form.  Of course this may be a fault of my own somewhere which I have yet to discover.  Until I figure out why things are bombing out I intend to make the encoder generate both forms for constructed TLVs.  This is why I have started the encoder-redesign branch with revision 36422.




---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira