Forum Discussion
dennypayne
Jun 18, 2009Employee
You would have to not redirect any element on the page to avoid the mixed content problem. Right now your logic prevents redirecting /paymentoptionshome/payments but that probably only covers the html on the page. I suspect that the images, css, etc. on that page have a different URI and are thus getting redirected to HTTP, causing the mixed content warning (understand that every element on the page is a separate GET and thus a separate connection that passes through the iRule).
Denny