08-12-2009 12:50 PM
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.
If they go to https://192.168.1.1/MyFolder/MyApp/ they are being redirected to 192.168.1.1 only.
is there a way to overcome this? maybe saving the URL portion in a variable and then pass it along the redicrection?
Thanks in advance.
Solved! Go to Solution.
08-12-2009 01:35 PM
Attached is a sample to achieve that
service HTTP2HTTPS
no prepend-http
keepalive type none
type redirect
domain https://www.yoursite.com
active
content HTTP2HTTPSrule
vip address 192.168.1.1
protocol tcp
port 80
url "/*"
add service HTTP2HTTPS
active
content HTTPS
vip address 192.168.1.1
protocol tcp
port 443
add service yoursslserver1
add service yoursslserver2
active
Thanks
Syed Iftekhar Ahmed
08-12-2009 01:35 PM
Attached is a sample to achieve that
service HTTP2HTTPS
no prepend-http
keepalive type none
type redirect
domain https://www.yoursite.com
active
content HTTP2HTTPSrule
vip address 192.168.1.1
protocol tcp
port 80
url "/*"
add service HTTP2HTTPS
active
content HTTPS
vip address 192.168.1.1
protocol tcp
port 443
add service yoursslserver1
add service yoursslserver2
active
Thanks
Syed Iftekhar Ahmed
08-12-2009 02:17 PM
Awesome, thanks Syed, I'll try the configs tomorrow to see how they work :)
08-13-2009 08:41 AM
Working perfectly, thanks a lot.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide