We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi all,
The new Websockets library does not use the path configuration variable, if I not using the uri scheme.
Initialization code:
esp_websocket_client_config_t ws_conf = { .host = URL, .port = PORT, .path = path, .buffer_size = 512, .transport = WEBSOCKET_TRANSPORT_OVER_SSL, };
Working solution: set path for transport before intialization
Current code (components/esp_websocket_client/esp_websocket_client.c; from line 430):
if (client->transport == NULL) { ESP_LOGE(TAG, "There are no transport"); client->run = false; break; } if (esp_transport_connect(client->transport, client->config->host, client->config->port, client->config->network_timeout_ms) < 0) { ESP_LOGE(TAG, "Error transport connect"); esp_websocket_client_abort_connection(client); break; }
Working code:
if (client->transport == NULL) { ESP_LOGE(TAG, "There are no transport"); client->run = false; break; } esp_transport_ws_set_path(client->transport, client->config->path); if (esp_transport_connect(client->transport, client->config->host, client->config->port, client->config->network_timeout_ms) < 0) { ESP_LOGE(TAG, "Error transport connect"); esp_websocket_client_abort_connection(client); break; }``` Regards,
The text was updated successfully, but these errors were encountered:
c0ba9e1
ws_client: fixed path config issue when ws server configured using ho…
b529c6f
…st and path instead of uri closes #3892
82282d7
…st and path instead of uri closes espressif/esp-idf#3892 * Original commit: espressif/esp-idf@c0ba9e1
cecdc23
No branches or pull requests
Environment
Problem Description
Hi all,
The new Websockets library does not use the path configuration variable, if I not using the uri scheme.
Initialization code:
Working solution: set path for transport before intialization
Current code (components/esp_websocket_client/esp_websocket_client.c; from line 430):
Working code:
The text was updated successfully, but these errors were encountered: