Anyone using Xojo.Net.HTTPSocket with POST method? It seems to be completely broken, the content (xojo.core.memoryblock) is there in the debugger but the socket never sends it with the request. Also the Content-Length header is always set to 0.
Ive made a bugreport for this, since you must have a server and look in the header received on the server side before youll ever notice this. The debugger wont show anything other than the ValidateCertificates property.
Windows 10 - Xojo 2018 R4
No release notes found about a change and 2018 R3 just works without problems.
FB case is made, will post the link later.
If you can confirm this to be broken please add a note, since it has broken 100s of api calls over here without notice.
The new [url=https://documentation.xojo.com/resources/release_notes/2018r4.html] URLConnection[/url] class (part of API 2.0) is an updated version of HTTPSocket and Xojo.Net.HTTPSocket used for web communications
This let me think your feedback will be rejected. But I can be wrong.
[quote=418935:@Emile Schwarz]From the Release Notes (Xojo 2018r4):
The new [url=https://documentation.xojo.com/resources/release_notes/2018r4.html] URLConnection[/url] class (part of API 2.0) is an updated version of HTTPSocket and Xojo.Net.HTTPSocket used for web communications
This let me think your feedback will be rejected. But I can be wrong.[/quote]
Yeah right, they broke the socket. As it DID work in R3, and stopped working in R4. Even tough the beta dudes didn’t notice it there should not have been a change. It’s clear that something did change.
And URLConnection is completely diffrent in Parameter types, Event names and such.
[quote=418938:@]Yeah something is definitely broken between 2018r3 and 2018r4 in Xojo.Net.HTTPSocket as this hacked up demo works in 2018r3 but hangs in 2018r4.
You can use it in the ticket if you want, as they like demos.[/quote]
i’ve added an example. could add this one though.
even better if more people respond to this in FB.