> Thanks for solution Baptise but why is it consider a dirty hack? I must > assume that it may cause problems in a more complex setups. >
Hi Pavlos, I considered it as a dirty hack because I "derouted" a feature from its original purpose and I knew there will be features in new release that would dedicated to what you want to do. And so, you should have update your configuration accordingly. That's what Willy mentionned: http-request capture rules from 1.6. Baptiste
