Skip to content

Conversation

@Ray0907
Copy link

@Ray0907 Ray0907 commented Aug 23, 2025

When a URL was provided without an explicit port, the client would fall back to the constructor's port parameter (default 6334), causing URLs like https://example.com to incorrectly use port 6334 instead of the standard HTTPS port 443. Now properly defaults to: - Port 443 for HTTPS URLs - Port 80 for HTTP URLs - Constructor port parameter for other protocols Fixes incorrect port resolution for standard HTTP/HTTPS URLs.

related issue: #94

…ly, when a URL was provided without an explicit port, the client would fall back to the constructor's port parameter (default 6334), causing URLs like https://example.com to incorrectly use port 6334 instead of the standard HTTPS port 443. Now properly defaults to: - Port 443 for HTTPS URLs - Port 80 for HTTP URLs - Constructor port parameter for other protocols Fixes incorrect port resolution for standard HTTP/HTTPS URLs.
@AMKamel
Copy link

AMKamel commented Sep 17, 2025

When will this fix get released?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants