Title: SSL connection to ClickHouse loses protocol prefix in edit form and incorrectly displays non-SSL port
Description:
Steps to reproduce
- Add a new ClickHouse connection with SSL enabled
- Fill in the connection details:
- Host:
https://192.168.0.165
- Port:
8443
- SSL: ON
- Click "Test connection" — works fine
- Save the connection
- Go back to connections list
- Observe the displayed connection string
- Click "Edit" on the saved connection
Expected behavior
- Connection should display as
https://192.168.0.165:8443 in the connections list
- Edit form should show the same host and port that were entered:
https://192.168.0.165 and 8443
Actual behavior
- In the connections list: shows
192.168.0.165:9000 (port changed to 9000, protocol prefix lost, equals sign appears)
- In the edit form: host field shows
192.168.0.165 (without https:// prefix), port shows 8443 (correct)
The connection works correctly after saving despite the display issues. The problem appears to be:
- The
https:// protocol prefix is stripped from the host field when saving or editing
- The default ClickHouse native protocol port (9000) is shown instead of the configured HTTPS port (8443)
Environment
- Dory version: latest (v0.19.4)
- Deployment: Docker
Title: SSL connection to ClickHouse loses protocol prefix in edit form and incorrectly displays non-SSL port
Description:
Steps to reproduce
https://192.168.0.1658443Expected behavior
https://192.168.0.165:8443in the connections listhttps://192.168.0.165and8443Actual behavior
192.168.0.165:9000(port changed to 9000, protocol prefix lost, equals sign appears)192.168.0.165(withouthttps://prefix), port shows8443(correct)The connection works correctly after saving despite the display issues. The problem appears to be:
https://protocol prefix is stripped from the host field when saving or editingEnvironment