update#1
Security Review Required
Summary: PR violates OCPP specification by changing WebSocket subprotocol from correct 'ocpp1.6' to incorrect 'ocpp-1.6', which will break protocol negotiation and prevent secure OCPP communication.
Critical Security Issues
1. Protocol Compliance Violation in src/MicroOcpp.cpp
WebSocket subprotocol changed from OCPP-compliant 'ocpp1.6' to non-compliant 'ocpp-1.6'. According to OCPP specification (Table 1), OCPP version 1.6 must use subprotocol name 'ocpp1.6' without hyphen. This will cause WebSocket handshake failures with compliant OCPP backend servers.
2. Protocol Compliance Violation in src/MicroOcpp.cpp
WebSocket subprotocol changed from OCPP-compliant 'ocpp1.6' to non-compliant 'ocpp-1.6' in non-TLS connection. According to OCPP specification (Table 1), OCPP version 1.6 must use subprotocol name 'ocpp1.6' without hyphen. This will cause WebSocket handshake failures with compliant OCPP backend servers.