Wildcard op / middleware about node-ldapjs

[mcavage]

Hi Falco,

So by wildcard operator, you mean "ignore the tree" altogether? I like the idea of a .use() paradigm (I kind of had something like that somewhere along the line, but it wasn't clear that most uses would want to implement all the LDAP operations, so I never got around to stubbing). I'm not sure that I like the idea of server.use(function(req, res, next)) without a mount point, since you would be effectively banning rootDSE, or any other logic (I almost always mount a handler for an admin user/group for example). But otherwise it should be doable.

m

[fnogatz]

Not just ignoring the tree but also the OP. For my use case a connect-like server.use('o=example', function(req, res, next){}) would be enough but I can image scenarios where you want do an action for every single request ignoring what it exactly does, e.g. logging.

[mcavage]

Oh - I forgot to mention, the common case (imo) for wildcarding the operation is "post" action items (i.e., log). So in master as of today or yesterday is a new .after() method that takes a chain of handlers that are guaranteed to be invoked after the last of your "normal" chains, regardless of whether an error was sent.

[fnogatz]

Okay, the .after() method is really a good way for post operations like logging. Nevertheless it would be nice to implement a server.use('o=example', function(req, res, next)) which would make proxying and caching easier.

[mcavage]

Yeah, not disputing that. I was just asking about server.use(function...) only :)

[dresende]

I missed this also, i.e., having a callback that would receive every OP request careless of that rdn is sent.

Question (can't test now): If I have a server.search("o=example", cb), will this receive requests for *, o=example or just o=example ?

[mcavage]

In that example server.search('o=example', function(req, res, next) {}) will match o=example and *, o=example (i.e., all children). The ldapjs "router" does dn.parentOf($requested_dn)

[dresende]

Great! All I needed to ear :)

[mcavage]

Wow, sorry I forgot about this one. It's in [email protected] now. There's a server.use() now:

server.use(function(req, res, next) { console.log('hi!'); return next(); });
server.search(...);

[fnogatz]

Hi Mark,
thanks, that's exactly what I (still) needed!