Hi,
Do we have an example for an "unique_uri strict" uri?
unique_uri strict ldap:///?mail?sub?
says this is invalid, but it it probably my misunderstanding of what it expects.
Thanks.
ghenry@OpenLDAP.org wrote:
Hi,
Do we have an example for an "unique_uri strict" uri?
unique_uri strict ldap:///?mail?sub?
says this is invalid, but it it probably my misunderstanding of what it expects.
I think the syntax is a bit odd, but that's how it's supposed to work:
unique_uri "strict ldap:///?mail?sub?"
that is: "strict" is part of the URI list arg.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------
----- "Pierangelo Masarati" ando@sys-net.it wrote:
ghenry@OpenLDAP.org wrote:
Hi,
Do we have an example for an "unique_uri strict" uri?
unique_uri strict ldap:///?mail?sub?
says this is invalid, but it it probably my misunderstanding of what
it expects.
I think the syntax is a bit odd, but that's how it's supposed to work:
unique_uri "strict ldap:///?mail?sub?"
that is: "strict" is part of the URI list arg.
Ah, that explains it. Do you this I should change:
unique_uri <[strict ][ignore ]URI[URI...]...>
to
unique_uri "<[strict ][ignore ]URI[URI...]...>"
then?
Gavin Henry wrote:
----- "Pierangelo Masarati" ando@sys-net.it wrote:
ghenry@OpenLDAP.org wrote:
Hi,
Do we have an example for an "unique_uri strict" uri?
unique_uri strict ldap:///?mail?sub?
says this is invalid, but it it probably my misunderstanding of what
it expects.
I think the syntax is a bit odd, but that's how it's supposed to work:
unique_uri "strict ldap:///?mail?sub?"
that is: "strict" is part of the URI list arg.
Ah, that explains it. Do you this I should change:
unique_uri <[strict ][ignore ]URI[URI...]...>
to
unique_uri "<[strict ][ignore ]URI[URI...]...>"
Well, the <> clearly indicates it's a single argument. Maybe an example, or a remark, would help not overlooking it.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------
unique_uri "<[strict ][ignore ]URI[URI...]...>"
Well, the <> clearly indicates it's a single argument. Maybe an example, or a remark, would help not overlooking it.
That's fine then. I just misread that syntax. Leave as is.
On Mon, Nov 24, 2008 at 03:57:35PM +0000, Gavin Henry wrote:
unique_uri "<[strict ][ignore ]URI[URI...]...>"
Well, the <> clearly indicates it's a single argument. Maybe an example, or a remark, would help not overlooking it.
That's fine then. I just misread that syntax. Leave as is.
Hmm - I think the syntax is sufficiently unusual that an example and note would save a lot of confusion.
I am also wondering what happens when the URI itself would need quoting when used alone - e.g. a URI with spaces in it. Do we need to put quoted quotes inside the overall quotes, or is the one set enough?
It would also be worth adding a note about *when* the unique_uri syntax became available (2.4.x). This sort of thing is useful when doing upgrades and also as a reminder when dealing with configs for older versions.
Andrew
Andrew Findlay wrote:
On Mon, Nov 24, 2008 at 03:57:35PM +0000, Gavin Henry wrote:
unique_uri "<[strict ][ignore ]URI[URI...]...>"
Well, the <> clearly indicates it's a single argument. Maybe an example, or a remark, would help not overlooking it.
That's fine then. I just misread that syntax. Leave as is.
Hmm - I think the syntax is sufficiently unusual that an example and note would save a lot of confusion.
I am also wondering what happens when the URI itself would need quoting when used alone - e.g. a URI with spaces in it. Do we need to put quoted quotes inside the overall quotes, or is the one set enough?
Well, this problem appears ever since in OpenLDAP. In ldap_initialize(), for example, and in back-ldap/beck-meta's URI directive. In those cases the problem is solved by requiring URL-escaping spaces (%20), which is the correct answer, although horribly unreadable (DNs already have their quirks, adding URL ones on top of them makes things worse).
If I were to redesign back-ldap/meta now, I'd use separate args for the URI list...
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------
If I were to redesign back-ldap/meta now, I'd use separate args for the URI list...
We should stick this on the OpenLDAP 3.0 Roadmap list.
openldap-software@openldap.org
-
Andrew Findlay -
Gavin Henry -
ghenry＠OpenLDAP.org
-
Pierangelo Masarati