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
(→Web Sockets) |
|||
| (9 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | =Load | + | =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>. 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 are 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 do not need to set up HTTPS between your load balancer and Web Services. | |
| − | + | {{NoteFormat|Web Services and Applications does not currently support web sockets.}} | |
| − | + | <!--Your load balancer must also support web sockets if they are used as the transport for unsolicited notifications in [[CometD|CometD]]. | |
| − | Your load balancer must support web sockets if they are used as the transport for unsolicited notifications in CometD. | ||
| − | + | {{NoteFormat|If you use Workspace Web Edition and your load balancer supports web sockets, you must enable this feature in Workspace Web Edition by setting the [[Documentation:HTCC:IWWDep:Application:8.5.2#system.notif.enabled-websocket|system.notif.enabled-websocket]] option to <tt>true</tt>.}}--> | |
| − | |||
| − | {{NoteFormat|If you use Workspace Web Edition and your load balancer supports web sockets, you must enable this feature in Workspace Web Edition by setting the [[Documentation:HTCC:IWWDep:Application:8.5.2#system.notif.enabled-websocket|system.notif.enabled-websocket]] option to true.}} | ||
[[Category:V:HTCC:8.5.2]] | [[Category:V:HTCC:8.5.2]] | ||
Latest revision as of 14:40, July 13, 2017
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 are configuring your solution to use Hypertext Transfer Protocol over Secure Socket Layer, you do not need to set up HTTPS between your load balancer and Web Services.