-
Bug
-
Resolution: Fixed
-
Medium
-
5.8.8, 5.9.4, 6.0.2
-
5
-
Severity 2 - Major
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
In CONF-3582 jkennemer noticed that SNI doesn't appear to be implemented in all parts of Confluence correctly. Specifically when setting up a gadget feed URL in Confluence, the Client Hello packet which is sent to the server does not include the SNI extension. Attached is a packet capture showing the TLS/SSL transaction in Confluence 6.0.2 when configuring a gadget feed, and also a packet capture for creating an Application Link.
This is important to fix as we have customers who may be running JIRA data center (or other applications) behind apache or nginx, and are expecting to parse this SNI extension.
- is related to
-
CONFSERVER-42948 Confluence SNI not working
- Closed
-
CONFSERVER-37582 Confluence should support the use of TLS - SNI
- Closed
- relates to
-
CONFCLOUD-45964 SNI is not working as expected in in Confluence Cloud
- Closed
-
JRASERVER-47568 Spurious SSL SNI errors in Jira server 7.0.2
- Closed
-
AG-1505 Loading...
- links to