Forum Discussion
Opher_Shachar_6
Sep 11, 2015Nimbostratus
Thats what a LTM Policy would look like:
ltm policy mycompany.com_policy {
controls { forwarding }
requires { http }
rules {
egift {
actions {
0 {
http-reply
redirect
location https://456.mycompany.com[HTTP::uri]
}
}
conditions {
0 {
http-host
host
values { 123.mycompany.com }
}
1 {
http-uri
path
values { /egift.aspx }
}
}
ordinal 1
}
}
strategy first-match
}
- Stanislas_Piro2Sep 11, 2015CumulonimbusI agree with you, policy is the easiest solution to redirect, assign pools, rewrite headers... The problem is the irule does exactly the same as your policy and does not solve the issue. that's why I asked marv Williams to explain what are differences between the initial request and the redirect URL.
- marv_Williams_5Sep 11, 2015NimbostratusThe values and placement of tid and eid chnage. I was hoping at least tid and eid would remain static. The request uses a number that the user has and they enter the entire url with the dynamic number. The redirect then contains new dynamic information after egift.aspx?. Also I am using 11.5.0 currently and did not think of policy but could try it
- marv_Williams_5Sep 11, 2015NimbostratusI mean dynamic content which is a series of letters and numbers
- marv_Williams_5Sep 11, 2015NimbostratusFurther clarification: - hostname changes from mycompany.com to egift.mycompany.com - uri remains egift.aspx all the way through -user enters dynamic content in the request (mycompany.com/egift.aspx?eid=xxxxxxx&tid=xxxxxxx and the is then redirected with new dynamic content. ex: egift.mycompany.com/egift.aspx?eid=a&tid=b Hope this makes sense?
- Opher_Shachar_6Sep 12, 2015NimbostratusNo. Doesn't make sense ... it's not clear who (or what) computes the new values of *eid* and *tid* from the old values.