gopalp I believe this is would be something that has to be tracked server side. You can perform a redirect after someone goes to https://abc.com/api-status to https://xyz.com but because this is most likely going to be a new session to a new FQDN the F5 isn't going to know how to interpret this and provide content to the user. You should be able to provide some sort of transaction ID, cookie, or referer that allows the xyz.com site to know that the user is looking for the contents of the output from abc.com/api-status.