How Can I control error connections on URLStreamBuffered?

[hash6iron]

Hi @pschatzmann ,

I try to knows when a connection failed with this below, but the process keeps in a loop without returning information.

My idea was use status returned by begin, but the process keep in begin always even when http_reques fails as you can see below.

Any solution? Thanks in advance.

                URLStreamBuffered urlStream(ssid.c_str(), password,1024); 
                ...
                logln("Tuning to station: " + radioName + " -> " + String(radioUrlBuffer));                
                if (urlStream.begin(urls[0]))
                {....}
                else
                {
                     logln("Error connection lost");
                }

Tuning to station: Vale Radio -> https://azura7.emisiononline.es/listen/vale_radio/radio.mp3

[I] URLStream.h : 80 - virtual bool audio_tools::URLStream::begin(const char*, const char*, MethodID, const char*, const char*): https://azura7.emisiononline.es/listen/vale_radio/radio.mp3
[I] Url.h : 59 - Url::parse
[I] Url.h : 97 - url->https://azura7.emisiononline.es/listen/vale_radio/radio.mp3
[I] Url.h : 98 - host->azura7.emisiononline.es
[I] Url.h : 99 - protocol->https
[I] Url.h : 100 - path->/listen/vale_radio/radio.mp3
[I] Url.h : 101 - port->443
[I] HttpRequest.h : 70 - stop
[I] URLStream.h : 360 - WiFiClientSecure
[I] HttpRequest.h : 240 - process connecting to host azura7.emisiononline.es port 443
...
[147005][E][ssl_client.cpp:129] start_ssl_client(): socket error on fd 50, errno: 113, "Software caused connection abort"
[147006][E][WiFiClientSecure.cpp:144] connect(): start_ssl_client: -1
[I] HttpRequest.h : 367 - is connected false  with timeout 60000
[E] HttpRequest.h : 243 - Connect failed
[I] HttpRequest.h : 316 - Request written ... waiting for reply
[I] HttpRequest.h : 181 - no CONTENT_LENGTH found in reply
[I] URLStream.h : 88 - contentLength: 0
[I] URLStream.h : 231 - Request written ... waiting for reply

[pschatzmann]

Please provide a simple example sketch where I can reproduce this...

[hash6iron]

At the end I saw that the problem is http request task that is in a loop until timeOut then is not possible to take the control of the program flow.

[pschatzmann]

Actually, when getting Connect failed we should not wait for a reply...
Unfortunatly your log does not contain any timing information, so I don't see where some waiting is going on...