2019R1 has critital fixes for bugs in Xojo.Net.HTTPSocket and URLConnection:
54757 Crashes & Assertions » IDE Unhandled Exception NilObjectException no longer occurs in some situations when debugging Xojo.Net.HTTPSocket .
54412 Framework » All Xojo.Net.HTTPSocket events are no longer raised on a pre-emptive thread, this would cause all sorts of random/odd behavior depending on the thread context switches.
54502 Framework » All Xojo.Net.HTTPSocket HTTP POST now properly sends the request content on Windows.
54811 Framework » All URLConnection Send requests are now closed before the ContentReceived or FileReceived events are called.
54820 Framework » All URLConnection string encoding for the Response headers are now consistent across platforms. Also updated the string encoding for the the content string, returned in ContentReceived, to adopt the content-type encoding (charset).
54927 Framework » All URLConnection now automatically handles compressed content-encodings on Windows and Linux (by decompressing for you like macOS does).
54592 Framework » Windows URLConnection now correctly honors the timeout when SendSync is called (instead of always defaulting to 30 seconds)
54608 Framework » Windows URLConnection error messages are no longer empty on Windows.
54685 Framework » Windows URLConnection ReceivingProgressed event now correctly reports the totalBytes.
54822 Framework » Windows URLConnection response headers are now updated correctly each time a request is made, where before subsequent requests would include outdated headers.
54907 Framework » Windows URLConnection picks up proxy settings correctly.
54410 Framework » macOS URLConnection.SendSync no longer intermittently returns empty strings.
But, 2019R1 also has a bad bug that causes HTTPSockets and URLConnections to be very slow and use lots of CPU - see Feedback Case #55301 . This bug is noted as being fixed for release in 2019R2. There's a workaround in the feedback case but it seems to barely work in my testing (speeds are still 1/5 or lower of what they should be).
I really want to use 2019R1 now - has anyone found a way to do so? I wish we could get a 2019R1.1 release. Any idea how long until 2019R2?