-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
When encoding the data chunk returned by the HTTP callback, parsing the body will fail. #1678
Comments
This problem has already been modified, please verify if the latest SRS3 still has this problem.
|
3.0.140 New version is normal
|
In version 3.0.141, I encountered the same error when using OBS for streaming. Upon observing the logs, I found that the connection was closed immediately after establishing a connection with SRS. Everything works fine when streaming without any configuration, but this issue occurs when configuring callbacks. The complete log when streaming with SRS is as follows: The configuration file used by SRS is as follows: }
|
Description
45
{"code":0,"token":"de53ddf1c533250c6a5ce1067e1a21e4a84ad1537634b48b"}
0
Description
Description
Description
#else
if (header.nread > 0)
consumed = header.nread;
#endif
Expectation: I don't know if the changes made are appropriate.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: