harton
Aug 22, 2011Nimbostratus
Common URI
I have a situation where I have a common portal for various customers. Customer A uses www.xyz.com/customerA and customer B uses www.xyz.com/customerB etc. The LTM directs the customers to their own app servers (customer A to pool A, customer B to pool B). There is a new feature that will be implemented, but the problem is that it's a common URI. When customer A clicks on the new feature, the application server replies back with a generic URI as www.xyz.com/nf. The exact same URI is given to customer B. The code can't be changed to make it www.xyz.com/customerA/nf. Is there a way for the LTM to send the data back to the correct pool when the URI has changed to a common one as above?