[Date Prev][Date Next]
*** Before acting on this email or opening any attachment you are advised to read the disclaimer at the end of this email ***
Some questions about the back-meta...
According to ITS 3785, any filter that cannot be successfully parsed is
rewritten to include "(!(objectClass=*))" before being propagated to any
target, always producing an empty result. My problem is that one of my
target servers throws a wobbly when it receives a query with this
filter, and takes around 15 seconds to respond with the empty result. Is
there any way of circumventing this behaviour?
Two of the target servers return search references for every query. As
these are of no use in this application, is there some way to stop
openldap from returning these references to the client?
Just out of interest, are there any plans to enable dynamic config
functionality for back-meta?
*** Disclaimer ***
The information contained in this E-Mail and any subsequent correspondence may be subject to the Export Control Act (ECA) 2002. The content is private and is intended solely for the recipient(s).
For those other than the recipient any disclosure, copying, distribution, or action taken, or omitted to be taken, in reliance on such information is prohibited and may be unlawful.
If received in error please return to sender immediately.
Under the laws of England misuse of information that is subject to the ECA 2002, is a criminal offence.
Westland Helicopters Ltd
Yeovil BA20 2YB
Registered in England under No 604352