Forum Discussion
Notanf5engineer
Nimbostratus
NimbostratusStandard irule that can be used for multiple urls
Here is a usecase I have and I am trying to find a solution for it. ABCD.com/app1/anything Translated to: app1.internaldomain.com/everything Abcd.com/app2/api/hello App2.internaldomain.com/API/he...
Paulius
MVP
MVPNotanf5engineer Is the app name always the same length or does it vary between a certain amount of characters? Sadly for this type of configuration you are better off configuring an iRule per virtual server based on what traffic you are sending to the virtual server. In all honesty you should really use the appropriate FQDN rather trying to move pieces of the URL around to meet the needs of each particular application. If you were provided a list of all the applications per FQDN you could create one virtual server with an iRule that references a data-group along with a FQDN match and then send them to the appropraite pool while keeping the iRule relatively short. Typically you would only want to result to using an iRule for this URL modification if for some reason these FQDNs had to be formatted the way you have stated.
Notanf5engineerNimbostratus
NimbostratusHi Paulius,
The appname varies. The reason why we are trying to create an appname.internaldomain.com is because the service hosts all the apps with a single ip in front but the hostnames vary..(if you are familiar with Azure App service hosted in an internal ASE)
I understand this is very esoteric. We were able to achieve a generalized irule for ip based pools. Since these are hostnames it gets very tricky. The issue with creating an irule per app is like we have around 80 apps and it might need similar functionality and managing all of them with different virtual servers and irules is lot of overhead but can be done.
Please let me know if you have any suggestions.
Thank you.