Ok, so I have this particular problem and I'm not sure if there's a way to overcome this.
I have a content rule which is listening to port 80 (let's say ip address 192.168.1.1), when that content rule is hit, the content rule redirects that query to port 443 in the same ip address (192.168.1.1) so we can always force they come to port 443 no matter what.
The problem I have is this, if someone hits https://192.168.1.1/MyFolder/MyApp/ it works fine, but when someone hits that same URL coming from port 80, the content rule redirects to the root.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...