Files
uptime-kuma/server/monitor-types
mkdev11 327b51f304 refactor: integrate TLS alert checking into TCP monitor
Per CommanderStorm's feedback, instead of creating a separate TLS monitor
type, add the TLS alert checking functionality directly to the existing
TCP monitor.

Changes:
- Add TLS_ALERT_CODES, parseTlsAlertNumber(), getTlsAlertName() to tcp.js
- Add checkTlsAlert() method to TCPMonitorType for mTLS verification
- Add 'Expected TLS Alert' dropdown to TCP monitor UI
- Remove separate TLS monitor type (tls.js)

This allows users to verify mTLS endpoints reject connections without
client certificates by expecting specific TLS alerts like
'certificate_required'.

Closes #5837
2026-01-06 20:28:09 +02:00
..
2026-01-06 02:37:05 -05:00
2026-01-06 02:37:05 -05:00
2025-05-18 22:35:55 +02:00
2024-06-14 16:44:36 -06:00