The traditional redirect will not give you the granularity you are looking for, however you can leverage http header rewrites in conjuction with the redirect to do "conditional" redirects.
I might be wrong, but I don't think a redirect is what you are looking for.. It sounds like the client is initially logging in via the ssl url then getting a redirect (from server) to http, which causes the client to "step outside" of the ssl channel and build a new session. More than likely the server is setting the location header to 'http://www.camko.com/honor/services.svc'.. What must do is keep the client connection over the ssl session buy doing an ssl rewrite. This way the web server's response is rewritten from http://www.camko.com/honor/services.svc to https://www.camko.com/honor/services.svc.
Example:
1) First add an action list:
!
action-list type modify http REWRITE-Location
ssl url rewrite location "www\.camko\.com"
!
2) policy-map type loadbalance first-match camko-443
!
class class-default
action REWRITE-Location <---- add under your HTTPS policy
serverfarm camko
!
3) You can then remove:
!
policy-map type loadbalance first-match camko
class class-default
serverfarm camko
policy-map type loadbalance first-match camko-redirect
class class-default
serverfarm camko-redirect
