Hello,

I noticed something that looks like a bug in the http package. When
trying to fetch a url, if the url exists but is not configured for
https, then a catch {http::geturl ...} will still create a pop-up error
window from inside a catch command. This happens despite registering
the tls socket. It says "Application Error" with the message "SSL
channel "sock05860970": error: tlsv1 alert internal error", with the bug
being that the catch did not catch it. I hope the description is clear.


package req http
package req tls
tls::init -tls1 1 -tls1.1 1 -tls1.2 1
http::register https 443 [list ::tls::socket]

# no error if protocol is http
# error if protocol is https
catch { http::geturl $host_with_no_https }

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Am 26.01.2022 um 22:08 schrieb [email protected]:

Hello,

I noticed something that looks like a bug in the http package. When
trying to fetch a url, if the url exists but is not configured for
https, then a catch {http::geturl ...} will still create a pop-up error window from inside a catch command.  This happens despite registering
the tls socket. It says "Application Error" with the message "SSL
channel "sock05860970": error: tlsv1 alert internal error", with the bug being that the catch did not catch it. I hope the description is clear.

package req http
package req tls
tls::init -tls1 1 -tls1.1 1 -tls1.2 1
http::register https 443 [list ::tls::socket]

# no error if protocol is http
# error if protocol is https
catch { http::geturl $host_with_no_https }

May you try the -timeout option.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 1/26/22 4:26 PM, Harald Oehlmann wrote:

Am 26.01.2022 um 22:08 schrieb [email protected]:

May you try the -timeout option.

Thank you. No, it did not make a difference.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)