Is net.HTTPClient() different in a scene or in a quiclkapp ?

[stipower 0]

Hi,

 

 

I noticed a different behavior between scenes and Qapps with net.HTTPClient().

This code works fine in my scene, but not in my Qapp. I have a 404 error, as if my passwords were wrong.

 

Is net.HTTPClient() different in a scene or in a quiclkapp ?

 

 

This is my QA code that does not work (404 error) : 

 

Please login or register to see this code.

 

Qapp debug  :

Please login or register to see this code.

 

This is my scene code that is working very well (302 code)

Please login or register to see this code.

 

scene debug:

Please login or register to see this code.

[jgab 2,642]

No, I think they should be the same. The json encode/decoder is different and behaves differently, but that's not your problem here... mostly issues with empty arrays...

The status 302 is a redirect that is tricky, but I don't think they should give a 404 back instead...

Another thought, the url in the QA is 

Please login or register to see this code.

 

and in the Scene

Please login or register to see this code.

The difference being the trailing slash - sometimes the server API can be picky about stuff like that.

[stipower 0]

Hi jgab,

 

Thanks for your answer.

 

The code 302 tells us that the syntax is ok.

The web server tell me to go on the special logged URL (when the credentials are correct) and to "/login/" (when credentials are wrong).

That is ok in a scene.

 

But I always have code 404 with a qapp.

 

I have created the same function to test my scene and my qapp.

It is exactly the same funtion.

I don't understand why the return status is not the same.

 

Can you test on your HC3 ?

 

QAPP :

Please login or register to see this code.

 

QAPP DEBUG :

Please login or register to see this code.

 

 

 

SCENE :

Please login or register to see this code.

 

SCENE DEBUG

Please login or register to see this code.

 

Edited February 19, 2025 by stipower

[jgab 2,642]

Yes, they do behave differently. Could it be that the QA implementation, to be "helpful", returns a 404 instead of a 302 because it won't do a redirect automatically?
The headers seems to be more or less the same with cookies and endpoints even if it returns a 404...

Alternatively, do an implementation with net.TCPClient and send a raw HTTP request and parse the raw result.

[stipower 0]

Hi,

 

I can try this.

But I have never implemented net.TCPClient.

Can you help me quickly to convet my lua code ?

[jgab 2,642]

Well, I just noticed that it's https, which makes it (too) complicated.

Fibaro has already all the components (luasocket and luasec) so it should be easy for them to support SSL sockets if they wanted.

[stipower 0]

Well, I am not sure to understand.

What should I try right now to fix it ?

Edited February 25, 2025 by stipower