sgcWebSockets 2024.10

[+] : Improved OpenAI Assistant, now allows to upload files and ask questions about the content of these files.
[+] : Improved OpenAI Assistant Demo, a new option has been added to upload files. The demo shows how to upload the sgcWebSockets.pdf manual and ask questions about it.
[+] : Improved sgcIndy Setup, new Option "Avoid Storing New Properties", if set to true, the new properties like APIVersion, LegacyProvider... won't be stored in the dfm files.
[+] : New property OpenSSL_Options.MinVersion to set which is the minimum version accepted.
[+] : Added support for Intraweb XVI.
[+] : Improved Amazon AWS S3 SDK, new method GetObjectAsStream to download the object as a binary stream.

[*] : Fixed Bug sgcWebSockets setup, when selecting Lazarus install some files where not exported.
[*] : Fixed Bug OpenAPI Parser when the result is a number.
[*] : Fixed Bug OpenAPI Client encoding the body as utf-8.
[*] : Fixed Bug memory leak when receiving fragmented messages, the internal queue object was not destroyed (Thanks to Jasja for letting me know).
[*] : Fixed Bug sgcIndy setting the minimum accepted tls protocol.
[*] : Fixed Bug HTTP/2 client when using the HTTP Proxy the SNI host was not set properly and the connection was closed.
[*] : Fixed Bug OpenAI Client parsing UTF-8 characters.
[*] : Fixed Bug MQTT Client memory leak when destroying the TsgcWSMQTTUNSUBACK class (Thanks to Robin for letting me know).
[*] : Fixed Bug WebSocket client would enter a loop if it encountered a 10054 error while connecting.
[*] : Fixed Bug AMQP1 Client the Hostname was not set properly.
[*] : Fixed Bug HTTP.SYS Server decoding WebSocket HTTP Headers when the connection comes from a reverse proxy. (Thanks to Corbinian for letting me know).

[/] : When selecting the openSSL Version tls1_3, now by default only the tls1_3 version will be accepted (before 2024.10.0 release, the tls1_2 was also accepted).

There is a new property to set the minimum tls version accepted, OpenSSL_Options.MinVersion. 

[*] : Fixed Bug memory leak when receiving fragmented messages, the internal queue object was not destroyed (Thanks to Jasja for letting me know).
[*] : Fixed Bug HTTP/2 client when using the HTTP Proxy the SNI host was not set properly and the connection was closed.

[*] : Fixed Bug WebSocket client would enter a loop if it encountered a 10054 error while connecting.