On Aug 1, 2006, at 3:02 AM, Dennis Dam wrote:
Ok, I tried posting the login form to "/url/to/current/page", and catching the request with a request matcher in the main sitemap. In flowscript I perform the login action, and then I redirect to cocoon://url/to/current/page again . But .. ofcourse the login request parameter is still there, so the redirect comes back to the same login flowscript, because of the request matcher. There is your infinite loop / internal server error.
Could you use a <select type="request-method> in your matcher to effect different handling for when the form is POSTed to the current page URI vs. the GET case (simple navigation or redirect from the login handler)?
—ml— --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
