Growtopia wont respond when using TLSe about tlse HOT 14 CLOSED

Hello,

From the debug output it seems that the connecion is correctly established (you receive the POST request). Also, you have the content-length set, but the actual content is missing. I think the problem is in the http server (the example is a simple less-than-minimal webserver). Maybe check if you received the full request before sending 404? If you test it from a web browser, what response do you get?

from tlse.

Hello,

From the debug output it seems that the connecion is correctly established (you receive the POST request). Also, you have the content-length set, but the actual content is missing. I think the problem is in the http server (the example is a simple less-than-minimal webserver). Maybe check if you received the full request before sending 404? If you test it from a web browser, what response do you get?

the result from browser is 404, and its work perfectly, but, on growtopia, it wont respond, i dont know why

from tlse.

is it problem on cipher? or the msg header?

from tlse.

okay, so when i try to check the cipher using Node JS

and the result is this

Is it possible to change the cipher in TLSe?

from tlse.

Hello,

From the debug output it seems that the connecion is correctly established (you receive the POST request). Also, you have the content-length set, but the actual content is missing. I think the problem is in the http server (the example is a simple less-than-minimal webserver). Maybe check if you received the full request before sending 404? If you test it from a web browser, what response do you get?

btw, on browser is work

from tlse.

hmmmm... when i try to check the Server Hello Length, its different

and the length between TLSe and Node JS (HTTPS Server) is different

is it okay or not?

from tlse.

Yes, it is perfectly fine. The difference is from the extension list (one is 23 bytes longer than the other). Most tls extensions are not mandatory, so no problem there.

from tlse.

Yes, it is perfectly fine. The difference is from the extension list (one is 23 bytes longer than the other). Most tls extensions are not mandatory, so no problem there.

ohh, is it possible to add that? so, i want to make the length byte same like node js

from tlse.

It is a little more complex than that. “Advertising” an extension implies support for it. The “renegotiation” extension is not required for a TLS connection. Also, keep in mind that the TLS layer is just fine, as shown in your first comment. The plain text data is fine. If you have had a problem with the TLS data and/or negotiation, you wouldn’t be able to see the plain text data (the POST data). Try to ensure that you read the whole data and your entire data is written before the socket is closed. I personally think that this is the problem. Keep in mind that the examples are not fully functional web servers (you need to write one or to use one).

As an experiment, add a sleep of about 1 second before closing the socket. Also, check the result of send/write APIs.

APPLICATION DATA MESSAGE (TLS VERSION: 303):
POST /growtopia/server_data.php HTTP/1.1
Host: www.growtopia1.com
User-Agent: UbiServices_SDK_2019.Release.27_PC64_unicode_static
Accept: /
Content-Type: application/x-www-form-urlencoded
Content-Length: 36

This means that your TLS negotiation and data layer are fine.

from tlse.

It is a little more complex than that. “Advertising” an extension implies support for it. The “renegotiation” extension is not required for a TLS connection. Also, keep in mind that the TLS layer is just fine, as shown in your first comment. The plain text data is fine. If you have had a problem with the TLS data and/or negotiation, you wouldn’t be able to see the plain text data (the POST data). Try to ensure that you read the whole data and your entire data is written before the socket is closed. I personally think that this is the problem. Keep in mind that the examples are not fully functional web servers (you need to write one or to use one).

As an experiment, add a sleep of about 1 second before closing the socket. Also, check the result of send/write APIs.

APPLICATION DATA MESSAGE (TLS VERSION: 303): POST /growtopia/server_data.php HTTP/1.1 Host: www.growtopia1.com User-Agent: UbiServices_SDK_2019.Release.27_PC64_unicode_static Accept: / Content-Type: application/x-www-form-urlencoded Content-Length: 36

This means that your TLS negotiation and data layer are fine.

i just add the sleep(1); before close the socket, its still doesnt work.

maybe i want to try to modify http library, like sandbird

from tlse.

I am using win32-c-http but, the growtopia still wont respond, i dont know why

from tlse.

I am using win32-c-http but, the growtopia still wont respond, i dont know why

even i add the Sleep(1000); code

from tlse.

Oh finally, its fixed, so, you right, i must add the Sleep() code, and make it to 0.5

from tlse.

Solved, thanks @eduardsui

from tlse.