Details
Description
Before Asterisk sends an HTTP response (at least in the case of errors), it attempts to read & discard the content of the request. If the client lies about the Content-Length, or the connection is closed from the client side before "Content-Length" bytes are sent, the request handling thread will busy loop. I tracked this down to the SSL handling in main/iostream.c.
I've attached a file that will help in reproducing this problem. You can test it against a running Asterisk 15 with the following:
cat reproduce.txt | openssl s_client -connect whatever.your.hostname.is.com:8089 -ign_eof
Once connected, just hit Ctrl-C and the Asterisk thread will start using 100% CPU.
Issue Links
- is a clone of
-
SWP-10296 Loading...
Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.
A good first step is for you to review the Asterisk Issue Guidelines if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the Patch Contribution Process.