It's been eons since I've had to do this, and I'm not sure if the
appliance config differs from the non-appliance config.

In the past, our "full" NAM server configuration required that we
front-end some stuff with a non-SSL proxy (ie, no authentication needed,
but the client software required non-SSL access). In the past, we've
had to bind a 2nd IP to the NAM LAG and then setup that parent IP (we
use DNS-based multi-homing) to do non-SSL.

Is that still the case for the appliance?

I'd need a secondary public IP setup for non-SSL (the parent/single IP
right now has the redirect 80 to 443).


kjhurni's Profile:
View this thread: