[ [url]http://issues.apache.org/jira/browse/DIR-184?page=comments#action_12375216[/
url] ]

Emmanuel Lecharny commented on DIR-184:
---------------------------------------

What we can do is to allow those leading and trailing '\ ', accordingly to t
he text : "Implementations MAY escape other characters."

A good solution could be to implement this document : http://www.ietf.org/proceedi
...apbis-dn-06.txt

It's section 2.4 states :
"... Alternatively, if and only if the character to be escaped
is one of

",", "+", """, "\", "<", ">", ";", "#", "=", or " "  <----- (has been added 
to RFC2253)
(ASCII 44, 43, 34, 92, 60, 62, 59, 35, or 32, respectively)

it can be prefixed by a backslash ('' ASCII 92). ..."

So the " " can be escaped.

Could you modify the JIRA report to be an improvment instead of a Major Bug?

> DnParser does not correctly parse leading and trailing spaces and pound si
gns in values.
> --------------------------------------------------------------------------
--------------
>
>          Key: DIR-184
>          URL: http://issues.apache.org/jira/browse/DIR-184
>      Project: Directory
>         Type: Bug

>     Reporter: Jacob S. Barrett
>     Assignee: Alex Karasulu

>
> As defined in RFC 2253 section 2.4:
> (http://www.ietf.org/rfc/rfc2253.txt)
> ..
> If the UTF-8 string does not have any of the following characters
>    which need escaping, then that string can be used as the string
>    representation of the value.
>     -   a space or "#" character occurring at the beginning of the
>         string
>     -   a space character occurring at the end of the string
>     -   one of the characters ",", "+", """, "\", "<", ">" or ";"
> ...
> A string can lead with '\ ' and trail with '\ '.  Both cases are not supported by 
the DnParser and cause a parsing error.  Furthermore, if a string starts with '\ ' o
nly the spaces leading up to the escape should be trimmed.  In addition only the spa
ces
after '\ ' when at the end of a value should be stripped.
> looking at the valuelexer.g file '\#' will work anywhere in the string, bu
t should really only be supported at the head of the string.
> If I understand the RFC correctly then these string should be supported:
> "\    four spaces leading and 3 trailing  \ " -> "\    four spaces leading
 and 3 trailing  \ "
> "    \  two leading three trailing  \    " -> "\  two leading three traili
ng  \ "
> "\# a leading pound" -> "\# a pound"
> "a middle # pound" -> "a middle # pound"
> "a trailing pound #" -> "a trailing pound #"
> These are not valid:
> "middle\ spaces"
> "# a leading pound"
> "a middle \# pound"
> "a trailing pound \#"
> Unless the next line in the RFC is really true, "Implementations MAY escape other 
characters."  This makes things a bit more hairy I think.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]