-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Post request return http status 100 #56
Comments
HTTP status 100 in the POST means that the client must send the body. |
What SourcePawn code do you use to get this status? |
Just if i send it to other apis, even if you take an example, everything works |
Strange, HTTP status 1xx should handle CURL inside RIP |
can I try something else |
Now result http status is 0 |
Try public void OnPostResponse(HTTPResponse response, any value, const char[] error)
{
PrintToServer("Data %i", response.Status);
PrintToServer("Error \"%s\"", error);
PrintToServer("way-way");
} |
Second, i make request on server "nginx" |
in fact, to test my theory, you can simply raise the test server to 443 |
He doesn't take info, because he send trouble request |
hostname - [09/Jul/2021:22:30:40 +0000] "POST /test/aaa.php HTTP/1.1" 400 25 "-" "sm-ripext/1.3.0" |
log from nginx |
Again, the joke is that if you throw on https, then everything is fine |
|
RiP will use HTTP/2 over HTTPS, if your server supports it. HTTP/2 does not use status code 100. As Wend4r said, status code 100 tells the client to send the request body, so I don't know why libcurl is not sending it. |
So what should I do in the end? |
everything is fine with GET requests |
Use HTTPS, if that works for you. Like I said, I don't know why it's not working, and I don't have time right now to look into it. |
Can be fixed with #68 |
When sending a post request to localhost: 3000, on which my web server is running on node.js, I get http status code 100, while throwing a request to my domain (to the server), there is already an nginx web server, I also get 100, but when I send a request to https, everything is normal.
The text was updated successfully, but these errors were encountered: