Forum Discussion
unRuleY_95363
Nov 22, 2004Historic F5 Account
First, the cryptic message should really read:
Multiple redirect/respond invocations not allowed (line 1) invoked from within "HTTP::redirect "http://${host}/foo/bar/baz"
What is happening is that your rule is first setting a HTTP::redirect because the host does not contain a ".". Then, later, you are again invoking a redirect because the path does not start with "/foo". You can only redirect once for a connection in a given rule. So, you could simply fix this by adding a "return" after the first redirect. Of course, depending on your application, you could also fix it by saving the redirect string off in a variable and then doing the redirect at the end of the rule event if the redirect variable is not empty.