Here's what's in my pipeline now:
<!-- This is the authentication resource -->
<map:match pattern="authenticate/user">
<map:act type="request">
<map:generate src="mocks/authtest.xml" />
<map:transform type="xslt" src="authentication/user-check.xsl">
<map:parameter name="query-string" value="{requestQuery}" />
</map:transform>
<map:serialize type="xml" />
</map:act>
</map:match> <!-- (see below...) -->
<map:match pattern="authenticate/good">
<map:act type="request">
<map:generate src="mocks/auth-good.xml" />
<map:serialize type="xml" />
</map:act>
</map:match>Normally, this would be in an "internal-only" pipeline, but for now I've left it accessible to help me debug it. I ran "curl" against the server to capture the output from the "authenticate/user" resource, and it looked absolutely fine:
<?xml version="1.0" encoding="ISO-8859-1"?>
<authentication><ID>42</ID></authentication>So, redirected the "curl" output into a file called "mocks/auth-good.xml", and set up the second pipeline.
When I change the handler to call for "authenticate/good" as the authentication resource, authentication works!
What could possibly be the problem here? I'm just stumped. It won't auth using "authenticate/user", but if I serve up as a static resource the exact same XML just as it was generated by "authenticate/user", it works. So "authenticate/user" works, apparently, and authentication works, but they aren't working together for some reason. I just don't get it.
Any help much appreciated! ~mark
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
