sipmsg: incorrect check for missing Content-Length
authorStefan Becker <chemobejk@gmail.com>
Fri, 12 Jul 2013 22:25:07 +0000 (01:25 +0300)
committerStefan Becker <chemobejk@gmail.com>
Sat, 13 Jul 2013 12:55:50 +0000 (15:55 +0300)
commitcc9ab98c4479acefd0d889fa6dca0661871eb237
tree6597b05d2a98e15b16f30d7625e821856504beaf
parentf44f07f5e28f973f1c3aa9d783d259fe349bd69e
sipmsg: incorrect check for missing Content-Length

Content-Length is only mandatory when Content-Type is present. This
isn't a problem for the purple backend, but the telepathy backend aborts
on fatal error messages.

Noticed with a 302 HTTP response during Office 365 EWS autodiscover.

(cherry picked from commit e627a0cadd672c5e9948dabf903545929c89cae6)
src/core/sipmsg.c