With help of inayathulla1, I created a policy in the SSL module that change the HTTP server's redirection to the HTTPS.
It works fine but, unfortunately when the packet comes to the browser it seems that SSLM module makes some modification in the Set-cookie field in the HTTP URL.
The original packet transmitted from the server has set-cookie value set to value JSESSIONID=25AF9A59D968276B879BA3C49E6663B9. When this packet comes to the browser it has the following cookie value SetCookieSESSIONID=25AF9A59D968276B879BA3C49E6663B9
Does anybody know what is the cause of this problem ?
Thanks in advance
I have already managed to solve the problem. I found that there were multiple entries in the url-rewrite policy, which overwrite each other, and when I deleted some of them the problem disappeared.
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...