FTS-2037: disable TLSv1.3 to fallback on TLSv1.2
Requiring a certificate to access the transfers logs, create a post-handshake scenario, which is not well handled by the clients using TLSv1.3.
For the moment, in absence of a better solution, disabling TLSv1.3 allows the users to access transfer logs without issues.
Merge request reports
Activity
Thanks Louis! This will do and will make the transition from CC7 to Alma9 smoother.
In the future, we can think about strictly requiring a client certificate for every page, not only for transfer logs. I remember you said this would no longer break the redirection from the Web Monit pages to the transfer log page.
Merging into
develop
!Cheers,
Mihaimentioned in commit 4638045e
Please register or sign in to reply