sipmsg: incorrect check for missing Content-Length
commite627a0cadd672c5e9948dabf903545929c89cae6
authorStefan Becker <chemobejk@gmail.com>
Fri, 12 Jul 2013 22:25:07 +0000 (13 01:25 +0300)
committerStefan Becker <chemobejk@gmail.com>
Fri, 12 Jul 2013 22:32:02 +0000 (13 01:32 +0300)
tree55c6c6ed7582e7d02490f1bd8460d10ec13cb74f
parent0f5cb722461ea9a3f3050ddbec959acd3dc05aed
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.
src/core/sipmsg.c