Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Packetbeat HTTP parsing fails on empty status phrase #6176
An HTTP response whose status phrase is empty causes the following error:
For example :
The response parser in https://github.com/elastic/beats/blob/master/packetbeat/protos/http/http_parser.go#L224 is expecting the status-phrase to be non-empty.
From this question on discuss.
The warning tells status:302 so the status seems to be parsed?
See my full log file for more examples: packetbeat.log
Packetbeat and tomcat running together in a docker-container. Maybe there is a problem with docker network because of logged messages "Ignore empty non-FIN packet"?
I was checking and testing this issue and about to commit it to my fork but it seemed to obvious to me where the issue might be that I'd rather leave the question in this issue before actually make a PR.
In the function
Let me know what you think about this change.