Hypertext Transfer Protocol Over Secure Socket Layer
Glossary:Hypertext Transfer Protocol Over Secure Socket Layer
Glossary
| Line 2: | Line 2: | ||
Web Services supports any third-party load balancer that supports sticky sessions. You should configure session affinity (sticky sessions) based on <tt>JSESSIONID</tt>. Once your load balancer is set up, you can use the following URL for health checks: <tt><nowiki>http://<Web_Services_Host>:<Web_Services_Port>/api/v2/diagnostics/version</nowiki></tt>. | Web Services supports any third-party load balancer that supports sticky sessions. You should configure session affinity (sticky sessions) based on <tt>JSESSIONID</tt>. Once your load balancer is set up, you can use the following URL for health checks: <tt><nowiki>http://<Web_Services_Host>:<Web_Services_Port>/api/v2/diagnostics/version</nowiki></tt>. | ||
| − | If you're configuring your solution to use {{Glossaryterm|term= | + | If you're configuring your solution to use {{Glossaryterm|term=Hypertext Transfer Protocol over Secure Socket Layer|addlink=true}}, you don't need to set up HTTPS between your load balancer and Web Services. |
{{NoteFormat|Web Services and Applications does not currently support web sockets.}} | {{NoteFormat|Web Services and Applications does not currently support web sockets.}} | ||
Revision as of 16:19, February 1, 2016
Load balancing
Web Services supports any third-party load balancer that supports sticky sessions. You should configure session affinity (sticky sessions) based on JSESSIONID. Once your load balancer is set up, you can use the following URL for health checks: http://<Web_Services_Host>:<Web_Services_Port>/api/v2/diagnostics/version.
If you're configuring your solution to use Hypertext Transfer Protocol over Secure Socket Layer, you don't need to set up HTTPS between your load balancer and Web Services.
Important
Web Services and Applications does not currently support web sockets.
Comments or questions about this documentation? Contact us for support!