On desktop clients, does the old HTTPSocket support TLS 1.2 on modern OSes that have this enabled?
I realize I should be using URLConnection. I need to know the answer to this to determine if I need to force every client to upgrade by the end of October when Azure stops supporting TLS 1.0 and 1.1.
Thanks!
AlbertoD
(AlbertoD)
September 30, 2024, 2:01pm
2
The documentation:
https://documentation.xojo.com/api/deprecated/httpsocket.html#httpsocket
says:
Description
Used to send and receive data via the HTTP 1.0 protocol.
for URLConnection:
https://documentation.xojo.com/api/networking/urlconnection.html
it says:
Description
Used to send and receive data using the HTTP 1.1+ protocol.
I hope URLConnection can do 1.2.
Thanks Alberto. To be clear, this is TLS which is separate from the HTTP protocols and sadly missing from the documentation.
1 Like
AlbertoD
(AlbertoD)
September 30, 2024, 2:07pm
4
Misread that. Sorry for the noise.
Edit: thank you Jeremie, so it is HTTPSecureSocket and not HTTPSocket, that got me confused.
Jeremie_L
(Jeremie_L)
September 30, 2024, 2:27pm
5
2 Likes
Thanks Jeremy.
According to the handy docs you referenced, it defaults to TLS 1.0.
However in my testing so far no TLS at all shows up when watching viewed in WireShark. Only HTTP. Will continue to check
AlbertoD
(AlbertoD)
October 2, 2024, 1:18pm
7
Just to be clear, that means that:
HTTPSocket does not support any SSL connection type
HTTPSecureSocket does support SSL connection type
Stephen Dodd:
However in my testing
The title says HTTPSocket. Are you using that or HTTPSecureSocket?