Topic
  • 2 replies
  • Latest Post - ‏2012-12-18T08:55:26Z by SystemAdmin
SystemAdmin
SystemAdmin
6772 Posts

Pinned topic Router rule action not redirecting the request to the new URL

‏2012-12-17T14:08:27Z |
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?
Updated on 2012-12-18T08:55:26Z at 2012-12-18T08:55:26Z by SystemAdmin
  • kenhygh
    kenhygh
    1577 Posts

    Re: Router rule action not redirecting the request to the new URL

    ‏2012-12-17T21:01:38Z  
    What's your rule look like? how are you trying to send to two different backends?

    Ken
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Router rule action not redirecting the request to the new URL

    ‏2012-12-18T08:55:26Z  
    • kenhygh
    • ‏2012-12-17T21:01:38Z
    What's your rule look like? how are you trying to send to two different backends?

    Ken
    We 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.