Forum Discussion
Hi Jason,
Thanks for your answer.
So here is the scenario. We have about 50 - 100 unique URIs that needs to be matched to a external redirect / path for each URI.
Note the "mysite.com" does not change
Note the "marketing-site.com" does not change, only the URI path for each customers are different as it is tailored and design for each customer differntly.
The Reason why we nee do to this is it is easier for the customer to go to our site and put in "https://mysite.com/CustomerA-Data" then to type
"https://marketing-site.com/CustomerA/.blah blah/ blah blah / blah blah/" -- Which is a very long, non-user friendly URL.
- Customer A ---> https://mysite.com/CustomerB-Data (Need F5 to look at URI and redirect to an external site with a specific URL allocated for that customer)
- Cusomter A --> Sent to by F5 based on URI match for this customer to --> https://marketing-site.com/CustomerA/.blah blah/ blah blah / blah blah/
- Customer B ....same thing where they go to "https://mysite.com/CustomerB-Data" ---> https://marketing-site.com/CustomerB/blah blah/ blah blah / blah blah/
Can i do something like this?
We need to use some sort of 1 to 1 mapping where Customer A needs to be sent to https://marketing-site.com/CustomerA/blah blah/ blah blah / blah blah/
and Customer B sent to "https://marketing-site.com/CustomerB/blah blah/ blah blah / blah blah/"..
Do you think an LTP is better as there will be 50-100 entries?
when HTTP_REQUEST {
if { [set redirect [class match -value "[HTTP::uri]" equals DG-URI-MATCH-REDIRECT]] ne ""}
then { HTTP::redirect "$redirect"
}
}