Details
-
Suggestion
-
Resolution: Fixed
-
None
Description
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
The idea is that we will assume that the proxy is started successfully, then we will do the health check for the proxy and log out any errors found.
Attachments
Issue Links
- is superseded by
-
CONFSERVER-45264 isSynchronyProxyRunning fails with javax.net.ssl.SSLHandshakeException
- Closed
- relates to
-
CONFCLOUD-45273 Remove the healthcheck for the synchrony-proxy webapp when Confluence is started up and monitor the proxy's running status
- Closed
- was split from
-
CONFSERVER-45271 With the the system property synchrony.proxy.enabled is set (to true), the proxy won't be enabled after a Tomcat restart until we restart Synchrony
- Closed