fix: Correct port when scheme is not provided

[chrizap]

provided

Signed-off-by: Christofer Gilje Skjæveland christofer.skjaeveland@zaptec.com

Describe your changes

This change ensures that URLs without an explicit scheme are handled correctly for security profiles 2 and 3.

Previously, when a URL like test.uri.com/path/ was provided under security profile 2, it would incorrectly resolve to wss://test.uri.com:80/path/cp0001. With this fix, it now falls back to the correct default secure port, resulting in wss://test.uri.com:443/path/cp0001.

Issue ticket number and link

Checklist before requesting a review

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• If OCPP 2.0.1 or OCPP2.1: I have updated the OCPP 2.x status document
• I read the contribution documentation and made sure that my changes meet its requirements

[Pietfried]

lgtm, thanks @chrizap