Forum Discussion

julien_bonnet4_'s avatar
julien_bonnet4_
Icon for Nimbostratus rankNimbostratus
May 02, 2018

Loadbalancing to node with different URI.

Hello,

 

I need some help with a specific need from the client. The F5 LTM is 11.5.3 version.

 

I don't really know if it's just url rewriting or loadbalancing, i don't know if i even have to create a pool that contain the member 10.128.66.65:9101 and 10.128.66.65:9103

 

The client want the flow to go like this

 

http://domainA.com/hod/v1/ to loadbalance to http://10.128.66.65:9101/apihod/v1/ http://domainA.com/media/v1/ to loadbalance to http://10.128.66.65:9103/apimedia/v1/ http://domainA.com/geo/v1/ to loadbalance to http://10.128.66.65:9101/apigeo/v1/

 

I can reach node url directly, it works, flow are opened between the F5 self and the node.

 

I tried to configure a rewrite profile URI redirection like this, but doesn't work :

 

Uri translation

 

REQUEST SETTINGS

Rewrite Headers Inset-X-Forwarded-For Header

 

RESPONSE SETTINGS

Rewrite Headers Rewrite content Any idea?

 

URI RULES

Rule type : Both

 

Client UrI : http://domainA.com/hod/v1/ Server URI : http://10.128.66.65:9101/apihod/v1/

 

Any idea?

 

Thank you.

 

1 Reply

  • You can ignore the "10.128.66.65:9101" part. Make sure the pool member is listening on port 9101 and the server is configured to handle "domainA.com".

     

    URL rewrite should be "/hod/v1/" to "/apihod/v1/".With iRule, you can use stringmap command.