Thanks, Vadim! See below...
From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]
Anyway, I'll wait a bit, and if nobody tells me I have my head up my b*tt I'll bugilla it. The bug, that is -- not my head (or my b*tt!)
Probably you are invoking this pipeline from a flowscript or cinclude transformer or sitemap aggregator (answer is somewhere in ... 27 more),
:-)
and due to misplaced head,
my head was "positionally challenged" :-)
:-)
you forgot to add global attribute:
<match pattern="*"> <redirect-to uri="http://foo.bar.com"; global="true"/> </match>
Actually it's not invoked from flow, cinclude or map:aggregate, but directly within a subsitemap.
I've seen a FileGenerator in the stacktrace which suggests that this url was part of some inclusion or aggregation. Which made me think that instead of redirecting internal included pipeline you intended to redirect outer pipeline - hence the need for the global.
Do you expect that global="true" fix that in this case?
Yup.
I'll give it a try when I get a chance (I ended up not needing this redirect after all).
Good riddance :-)
Vadim
