Graham Leggett wrote: > > "Christopher R Key (Chris)" wrote: > > > Based on what Ian and Graham have mentioned, it doesn't see as though > > the ldap proxy will be a complete proxy (like Innosoft's directory > > access router). Am I mistaken? > > Depends on your definition of "complete proxy". The standard "proxy" way > of handling things seems simplistically to be: > > - open up a tcp connection to proxy > - say GET <URL> HTTP/1.1 > - say Host: <hostname:port>\n\n > - Get some data back > > In the case of the LDAP proxy we simply now understand ldap: URLS in > addition to http: and ftp: URLs as we do now.
I believe I understand now. Instead of proxying ldap (ldap://myproxy => ldap://backend) you'll be making a macro or shortcut for ldap searches via http. Correct? -- Chris -- Non-Reciprocal Laws of Expectations: Negative expectations yield negative results. Positive expectations yield negative results.
