Forum Discussion
NimbostratusNew URL's wanting to be created
NoctilucentDo you actually want to perform HTTP redirects for all of these, or do you just want to route traffic to certain destinations based on protocol and port?
If the latter, I'd recommend you just setup virtual servers (all with the same VIP) listening on your desired different ports, and apply the proper pools containing the destinations you want to send the traffic. For example:
Virtual server listening on TCP port 443 -> pool with member server1 listening on 443 Virtual server listening on TCP port 1935 -> pool with member server2 listening on 1935 Virtual server listening on TCP port 9292 -> pool with member server3 listening on 9292 Virtual server listening on TCP port 5080 -> pool with member server2 listening on 5080 Virtual server listening on UDP all ports -> pool with member server2 listening on all service ports
Robert_Roman_14More to direct traffic to the appropriate servers. This is for a virtual care collaborator where doctors connect to a computer with a microphone and headphones and a camera and can have a video conference with another doctor at another hospital. As long as they can go to the URL it will open the website but we want to direct the traffic to certain servers to handle the differing traffic.- Robert_Roman_14However, when they access https://vcc-demo.company.com -that does perform an http redirect to server 4. I dont know if that adds into the equation much more or any
- Cory_50405What I've specified above should work for you, but I have a question about your server4. If you're going to redirect to that host, it'll need to have an FQDN to specify in the HTTP 302. Is there a FQDN setup for this redirect already?
