Forum Discussion
Hello,
Thank you all for your propositions :). They seems all interresting, for me. hmmmm I had a call this morning, after I created this topic. The application's guys seems to have a solution to fix it by doing a change on the server, side cloud. I will see if that really fix the problem.
But I have a question, anyway. If we apply the F5's KB I mentionned, we will replace the IP by HTTP::header replace "Host" "smartfqdn.sevenxxi.net" } (to take this example), but... the F5 will not try to replace again the "smart..." by the IP, following the configuration in the traffic policy ? I do not know if I am clear, as I am newbe on F5....
Oh wait a second, I think I understand. Normally, it should work like that, if we apply this KB, if I am not wrong :
1/ The request come to the F5. With the traffic policy, it will redirect the request to the IP.
2/ In the same time it will change the Header following the "kb's" irule.
3/ And when the request will arrive to the server, it will arrive with the good address, the good url, actually, to the server of destination, then the application web.
All right, in first view that could be a solution. But... Here, we are in this situation : the virtual server is attached to a lot of redirections HTTP, by his traffic policy. That mean all the requests sent to the same virtual server, so the same IP, let's say 10.18.10.104, will be transformed with the new header, doesn't matter if they are originally sent to "smart..." (or anything else), no ?
Thanks to Paulius and Zamrooni, too. I see what you mean, Paulius. Maybe that could work too. However, Zamrooni, can you develop what you mean by " you need to inform the application team to always use relative paths in the application codes" ? Just to clarify.