While trying to connect to two different URL's at the backend, the 'Router' action in the mpg is not redirecting the request to the new URL.
Could you please suggest anything in this regard. Are we missing something somewhere?
This topic has been locked.
2 replies Latest Post - 2012-12-18T08:55:26Z by SystemAdmin
Pinned topic Router rule action not redirecting the request to the new URL
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-18T08:55:26Z at 2012-12-18T08:55:26Z by SystemAdmin
kenhygh 120000PD1B1427 Posts
SystemAdmin 110000D4XK6772 PostsACCEPTED ANSWER
Re: Router rule action not redirecting the request to the new URL2012-12-18T08:55:26Z in response to kenhyghWe have put up 3 rules. In the first rule we are using set variable action to point to the primary link. The second rule is an error rule (which is called in case the primary link is down). The error rule simply redirects the request to the 3rd rule. The 3rd rule is similar to the 1st one except that we are setting the secondary URL in this one now. The scenario is that DP is setting the secondary URL correctly (in case the primary is down), but throwing the error response failed due to non idempotent request method - RFC 2616 sec 10.3. Could you please suggest how to resolve this issue.
Note: The request is an Http POST.