pidgin/pidgin

Improve how our HTTP proxy code reads the content-length header.
release-2.x.y
2014-01-12, Mark Doliner
dd8ee564e065
Improve how our HTTP proxy code reads the content-length header.

It now reads the length into an unsigned variable. This was reported
to us by Matt Jones of Volvent. I think there's no potential for
remote code execution or remote crash--we don't allocate a buffer
for the content or anything. I think it's just ugly code. I didn't
impose a max size for the content-length. I feel like it's ok for the
while loop to loop many times then get EAGAIN and break out.

I'm looking forward to unified http parsing in 3.0.0.
For information on writing a plugin for Purple, Pidgin or Finch, go
http://developer.pidgin.im and click on API. From there, see the
HOWTOs in the "Related Pages" section.
You can also generate this documentation locally by installing
doxygen and graphviz dot, then running "make docs" in the
source tree. The documentation will be in the docs/html directory.