Netscaler Knowledgebase

Since you didn't post an example of your rewrite rules, it's a bit hard to diagnose the bind error.
However, there are several ways to accomplish this request and below is how I've accomplished this in the past. This is a basic redirect http://mysite.com to https://mysite.com and doesn't take into account anything in the path of the request. So http://mysite.com/login.php would get redirected to https://mysite.com/. There are other ways handle that type of redirection.

My old way (easiest?).
- Create a LB vserver with the same IP on port 80 and don't bind anything as a service, then you can use the redirect (under Advanced) to the https://<url>. This would force all requests to be redirected to the SSL vserver. My problem with this method is that it leaves a nice red icon in your GUI as if something is down.

This is how I currently configure my http-https redirects for sites that are entirely SSL.
 - Create  a responder action force a redirect with the target of "https://<domain>"
 - Create a responder policy to bind that responder action with an expression of "TRUE".
 - Create a Content Switching vserver with the same IP as the SSL vserver and bind the responder policy to that vserver.

This should leave a service as enabled (nice and green) while redirecting all HTTP requests with a 302 to https://<site>

Ok, I made the HTTP VS a Content Switching VS - and now it accepts connections, but it's not doing anything but returning a "HTTP/1.1 Service Unavailable."  Here are the exact rules that I am using:

> add responder action responder_action1 redirect '"https://site.com" + HTTP.REQ.URL.PATH'
> add responder policy responder_policy1 'HTTP.REQ.HEADER("Host").CONTAINS.("site.com")' responder_action1
> bind cs vserver httpvsname -policy responder_policy1 -priority1

Any ideas?