Forum Discussion
HTTPS
- Sep 14, 2015
It looks like there are two things you need to modify here in your config:
- setting the service types to HTTP from TCP on all VIPs/VSs/RSs
- configure the virtual server VIPs to be defaults
Here is a summary of what you will need to update in the configuration. Keep in mind, you will need to admin-offline these items before being able to change service type.
virtual-server vsSecondary attach virtual-ip vipSecondary default virtual-server vsSecondary1 service http attach virtual-ip vipsecondary1 default real-server rss-rep1 service http virtual-ip vipsecondary1 service http virtual-server Webssilo1 attach virtual-ip vipsweb1 default
Doing this, I was able to replicate your configuration and successfully pass traffic to the original servers and replication servers for both HTTP and HTTPS. This should get you up and running, too.
i think the simple way is to add client ip header at the linerate manager but i tried 'X-Forwarded-For' or x-client-ip or clientip but it didn't work
also when i start to add my production server [Apache server] as real server https requests gives me "Status 502 Bad Gateway" however i added another IIS server and it works great. is there any additional configuration ?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com