Hi Dave,
You are missing just one command...
server real <server>
port <port#> concurrent
=== manual ===
The concurrent feature allows a client to have sessions on different
application ports on the same real server at the same time. When you
enable an application port to be concurrent, the real server can open
additional (“concurrent”) TCP/UDP sessions with the client using
arbitrary TCP/UDP port numbers. Although the concurrent connections
attribute is similar to application groups, application groups apply
to specific TCP/UDP ports that you configure on the virtual server.
NOTE: For servers that use passive FTP, configure the FTP ports to be
both sticky and concurrent.
To enable an application port to be concurrent, enter commands such as
the following:
ServerIron(config)# server virtual-name v1 209.157.22.1
ServerIron(config-vs-v1)# port 80 concurrent
Syntax: [no] port <tcp/udp-port> concurrent
=== manual ===
Mischa
On Mar 25, 2009, at 15:01, David Miller wrote:
We're trying to get a pair of ServerIrons installed. One thing they
have to do is handle what we used to call "port following" - where a
user is on http, then goes to ssl for authentication, then back to
http for the rest of their site administration.
That all needs to be a "session" on a single real server. It
*looks* like an application group should cover it, but it doesn't
seem to - ssl doesn't always follow http, and vice-versa.
Here's the config code I tried:
server virtual vserver 12.34.56.78
sym-priority 110
predictor round-robin
port http sticky
port ssl sticky
port ssl ssl-terminate Vserver
track-group http 443
bind http rserver1 http rserver2 http
bind ssl rserver1 ssl rserver2 ssl
Am I missing something simple here?
Thanks,
--- David
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
