Hypertext_Transfer_Protocol_over_Secure_Socket_Layer
Also known as https. A secure version of the Hypertext Transfer Protocol, it is the combination of a normal HTTP interaction over an encrypted Secure Sockets Layer (SSL) or Transport Layer Security (TLS) connection.
Glossary
(Update with the copy of version: 8.5.2DRAFT) |
(Update with the copy of version: 8.5.2DRAFT) |
||
| Line 1: | Line 1: | ||
=Load balancing= | =Load balancing= | ||
| − | Web Services supports any third-party load balancer that supports sticky sessions. You should configure session affinity (sticky sessions) based on <tt>JSESSIONID</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=Hypertext_Transfer_Protocol_over_Secure_Socket_Layer|text=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 18:22, March 25, 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.