| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
| |
These only reflect on what arch/cpu bitlbee was built, not on which
it is running. This makes the Debian package unreproducible.
See e.g.
https://tests.reproducible-builds.org/rb-pkg/testing/i386/bitlbee.html
|
|
|
|
|
|
|
|
|
|
| |
Twitter and MSN are all HTTP/SSL, so they don't need it either.
The out of tree facebook and steam plugins are also covered by the
HTTP/SSL changes.
Yahoo is written in a weird way and doesn't seem to need it (it seems it
doesn't immediately stop connections when you tell it to logout)
|
|
|
|
|
|
|
|
|
| |
Check callback function supplied to http_dorequest and only run it if it is
not NULL.
While it is not the usual case there are some times when there is no need to
check the results of a http request. Using a NULL pointer is much more
convenient than creating noop functions.
|
|
|
|
|
|
|
| |
Used uncrustify, with the configuration file in ./doc/uncrustify.cfg
Commit author set to "Indent <please@skip.me>" so that it's easier to
skip while doing git blame.
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes warnings about passing signed chars to them (apparently they
are implemented as macros that do array lookups without checks in some
platforms, yay)
Specifically:
functions=isalnum|isalpha|isdigit|isspace|isxdigit|tolower|toupper
sed -ir "s/$functions/g_ascii_&/g" **/*.c
|
| |
|
|
|
|
|
| |
- http_incoming_data calling itself
- jabber_bs_free_transfer calling jabber_si_free_transfer
|
|
|
|
|
|
|
| |
These appear in glib 2.40, and, well, are pretty much useless. But
people complain about them anyway.
Probably fixes trac ticket 1151, at least partially.
|
|\
| |
| |
| |
| |
| |
| | |
Little benefit as I'm not burning my fingers on keepalive connecitons for
now, but eventually the Twitter streaming API is going to drop 1.0 support:
https://dev.twitter.com/blog/deprecating-http-1.0-streaming-api
|
| |
| |
| |
| |
| | |
used protocol version when internally handling redirects.
|
|/
|
|
|
|
| |
let me close #641, and more importantly, prepares the Twitter module for
an upcoming API change. https://dev.twitter.com/blog/deprecating-http-1.0-streaming-api
|
| |
|
|
|
|
|
| |
Forgot to do this so far because my libevent code let me get away with it.
|
|
|
|
|
|
|
|
|
| |
MTU in mind it's not a very useful change, but I seem to be getting data in
bigger chunks most of the time. Likely because with SSL you have record (?)
boundaries and compression.
This should reduce I/O overhead just a little bit.
|
| |
|
|
|
|
|
| |
http_close().
|
|
|
|
|
|
| |
fixed URL and tried to parse individual JSON objects. Not doing anything
useful with it.
|
|
|
|
|
| |
a complete response before giving it back to the caller.
|
|
|
|
|
|
|
|
| |
least have a work-around for it.
After hitting the Twitter timer a few times while a previous fetch still
seems to be running, close the connection. Auto-reconnect will do the rest.
|
|
|
|
|
|
| |
be getting truncated sometimes. Treat this as an error in http_client
already instead of returning partial data.
|
|\ |
|
| |
| |
| |
| |
| | |
(Think of Twitter, but also MSN/Yahoo! authentication.)
|
|/ |
|
|
|
|
|
|
| |
is required for identi.ca and really should be done for Twitter as well.
Twitter OAuth is still broken though, it seems to disagree about signatures.
|
| |
|
| |
|
|
|
|
|
| |
truncate request if we switched from POST to GET.
|
|
|
|
|
|
| |
http_client module needs some refactoring though. Will do that later..
This should hopefully fix bug #850.
|
|
|
|
|
| |
which http_client really can't deal with.
|
|\ |
|
| |
| |
| |
| |
| | |
not a secret (the pointer is shared with a type later anyway).
|
| |
| |
| |
| |
| | |
be an end.
|
|/
|
|
|
|
|
|
|
|
| |
diverged too much this is fairly transparent. I did rename and redefine
GAIM_INPUT_* variables to really make it work without adding another stupid
layer in between.
One problem left, the new libpurple input API doesn't care about return
values. Fixing that in the next CL.
|
| |
|
|
protocols/, and adding RC4 code.
|