-
Notifications
You must be signed in to change notification settings - Fork 72
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
httpParserOnStatusCallback() is not called #171
Comments
It seems that the underlying parser does not invoke |
@TakCodeIT Also, can you share which server returns this response? |
Thank you for the patch. It works! |
I'll get back to you when I know the details. |
@aggarg Apparently, Tomcat is used for the server. |
on_status callback is not called for a response with a status code but without a reason string such as following: ``` HTTP/1.1 400 Server: nginx Date: Fri, 05 Jan 2024 05:25:21 GMT Content-Type: application/json Content-Length: 30 Connection: keep-alive ・・・ ``` It was reported here - FreeRTOS#171 Signed-off-by: Gaurav Aggarwal <[email protected]>
on_status callback is not called for a response with a status code but without a reason string such as following: ``` HTTP/1.1 400 Server: nginx Date: Fri, 05 Jan 2024 05:25:21 GMT Content-Type: application/json Content-Length: 30 Connection: keep-alive ・・・ ``` It was reported here - #171 Signed-off-by: Gaurav Aggarwal <[email protected]>
Fix has been merged in this PR - #173. Closing this issue. |
httpParserOnStatusCallback() is not called if a server returns a status code without a reason string such as following.
If a server returns "HTTP/1.1 400 Bad Request" instead of "HTTP/1.1 400", httpParserOnStatusCallback() is called.
The text was updated successfully, but these errors were encountered: