Forum Discussion
Hi Nikoolayy1,
thank you for the hint. Unfortunately this setting only overwrites the host header. I.e. if the target/application server sends a 302 redirect back to itself and not to the FQDN/IP of the XC, the subsequent request is not routed via the XC, but a direct connect to the corresponding target server is performed.
-------------------------------------------------------------------------------------
Example:
FQDN-XC: www[.]test.ves.io
FQDN destination: www[.]test.de
REQUEST www[.]test.ves.io/redirect/uri => XC => www[.]test.de/redirect/uri
RESPONSE 302 - Location: www[.]test.de/destination/uri => XC
===> At this moment XC have to rewrite the Location header to it's own FQDN (Location: www[.]test.ves.io/destination/uri)
-------------------------------------------------------------------------------------
The only particular solution i found is to send all redirects directly for defined uris, but that is not usefull in all cases.
I forgot to add that you can open a feature request at https://www.f5cloudideas.com/
- devd4nAug 30, 2023Altostratus
It allready exists 😉 i posted it inside the question 😉
https://www.f5cloudideas.com/ideas/MESH-I-149
nevertheless many thanks 🙂- Nikoolayy1Aug 30, 2023MVP
Didn't see it. Sorry 😀