Closed GuckTubeYT closed 1 year ago
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?
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
is it problem on cipher? or the msg
header?
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?
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
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?
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.
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
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.
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_unicodestatic 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
I am using win32-c-http but, the growtopia still wont respond, i dont know why
I am using win32-c-http but, the growtopia still wont respond, i dont know why
even i add the Sleep(1000);
code
Oh finally, its fixed, so, you right, i must add the Sleep()
code, and make it to 0.5
Solved, thanks @eduardsui
Hello, i want to make Growtopia HTTPS Server using TLSe, but, Growtopia didnt respond the HTTPS Server?
When i am using Node JS, Its work, but, when i am using TLSe, it didnt respond
Node JS
TLSe
I am using https://github.com/eduardsui/tlse/blob/master/examples/tlssimpleserver.c for the example and i am change the msg
const char msg[] = "HTTP/1.1 200 OK\r\nContent-length: 31\r\nContent-type: text/plain\r\n\r\nHello world from TLSe (TLS 1.2)";
to
const char msg[] = "HTTP/1.1 404 Not Found\r\nContent-length: 31\r\nContent-type: text/plain\r\n\r\nHello world from TLSe (TLS 1.2)";
i make it to
404 Not Found
to Check the Growtopia is Respond the TLSe or not, but the Growtopia still not respond the TLSeDebug Log
Build command
gcc tlssimpleserver.c -lws2_32 -lwinmm -DTLS_AMALGAMATION
Please help me