Steven,
As Hugh mentioned earlier, the AddToReplyIfNotIncluded directive takes the list
of parameters passed to it and looks at your reply packet. It takes the first
attrib from the list and looks for it in the reply packet, it finds no
Ascend-Data-Filter attribute and thus adds the attribute. It then takes the
second parameter from the list (another Ascend-Data-Filter) and looks for it in
the reply packet. It finds the Ascend-Data-Filter that was added just before
and thus doesn't add any further Ascend-Data-Filter attribs.
Solution: patch the code to Allow multiple Ascend-Data-Filters attribs if you
add one OR add a directive AddFilterToReplyIfNotIncluded which does exactly
this.
Your first mail on this subject caught my attention as I wanted to use this
solution for a new customer. As you found, it doesn't work and I'm looking at
modifying the code to support the latter solution. It isn't that much work, it
just needs to be done and to be tested and my todo list is long enough already.
I'll send the patch to the list when I get around to that item on my list.
- Joost.
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
