thanks for the report. I've added a small patch against 1.5.0 that should check for the null-pointer condition you observed. Would be great if you could test if this fixes the problem for you.
Henning
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it helped. I used similar workaround before. Unfortunately some devices send headers without Content-length but now these don't make the daemon crash anymore. Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
backtrace and content of *msg
null pointer check
Hi,
thanks for the report. I've added a small patch against 1.5.0 that should check for the null-pointer condition you observed. Would be great if you could test if this fixes the problem for you.
Henning
Do you was able to test the patch?
Yes, it helped. I used similar workaround before. Unfortunately some devices send headers without Content-length but now these don't make the daemon crash anymore. Thank you.
Ok, thank for the reply. I'll then commit this change to the 1.5 branch and master git tree.