Xojo.Net.HTTPSocket POST

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.

I’ve made a bugreport for this, since you must have a server and look in the header received on the server side before you’ll ever notice this. The debugger won’t 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 100’s of api calls over here without notice.

By the way URLConnection does work, but has different event names and parameter types so changing is alot of work.

<https://xojo.com/issue/54502>

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=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.

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.

https://www.dropbox.com/s/d8p8i6d3phgcuq9/TestXojoNetHTTPSocket2.xojo_binary_project?dl=1

You can use it in the ticket if you want, as they like demos.

[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.

https://www.dropbox.com/s/d8p8i6d3phgcuq9/TestXojoNetHTTPSocket2.xojo_binary_project?dl=1

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.

It might muddy the waters as I actually get POST content back it just breaks in the follow up GET, but I’ll add it as its clearly different/broken.

You get content using post? With Content-Length set to 0 or a actual number? And on windows? Cause MacOS just works as always.

  • reUsing xojo net httpsocket is practicly unsupported.

Yeah, give the code a try, see if its doing anything differently than you are?

I see the problem now Derk, I’ve just uploaded a clearer demo to the ticket, hope you don’t mind.

No the more the better, thanks. This is a Major issue for us.

It is an important problem indeed, I added my points.

There’s definitely something broken:
https://forum.xojo.com/51550-xojo-net-httpsocket-broken-with-r4

Unfortunately I still had no time so far to investigate it further.

[quote=420414:@Stefan Adelsberger]There’s definitely something broken:
https://forum.xojo.com/51550-xojo-net-httpsocket-broken-with-r4

Unfortunately I still had no time so far to investigate it further.[/quote]

Post doesn’t send the content on windows and doens’t set the content-length header. Major bug in 2018 R4.