/usr/include/bitlbee/http_client.h is in bitlbee-dev 3.0.4+bzr855-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 | /********************************************************************\
* BitlBee -- An IRC to other IM-networks gateway *
* *
* Copyright 2002-2005 Wilmer van der Gaast and others *
\********************************************************************/
/* HTTP(S) module */
/*
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
*/
/* http_client allows you to talk (asynchronously, again) to HTTP servers.
In the "background" it will send the whole query and wait for a complete
response to come back. Right now it's only used by the MSN Passport
authentication code, but it might be useful for other things too (for
example the AIM usericon patch uses this so icons can be stored on
webservers instead of the local filesystem).
Didn't test this too much, but it seems to work well. Just don't look
at the code that handles HTTP 30x redirects. ;-) The function is
probably not very useful for downloading lots of data since it keeps
everything in a memory buffer until the download is completed (and
can't pass any data or whatever before then). It's very useful for
doing quick requests without blocking the whole program, though. */
#include <glib.h>
#include "ssl_client.h"
struct http_request;
/* Your callback function should look like this: */
typedef void (*http_input_function)( struct http_request * );
/* This structure will be filled in by the http_dorequest* functions, and
it will be passed to the callback function. Use the data field to add
your own data. */
struct http_request
{
char *request; /* The request to send to the server. */
int request_length; /* Its size. */
int status_code; /* The numeric HTTP status code. (Or -1
if something really went wrong) */
char *status_string; /* The error text. */
char *reply_headers;
char *reply_body;
int body_size; /* The number of bytes in reply_body. */
int finished; /* Set to non-0 if the request was completed
successfully. */
int redir_ttl; /* You can set it to 0 if you don't want
http_client to follow them. */
http_input_function func;
gpointer data;
/* Please don't touch the things down here, you shouldn't need them. */
void *ssl;
int fd;
int inpa;
int bytes_written;
int bytes_read;
};
/* The _url variant is probably more useful than the raw version. The raw
version is probably only useful if you want to do POST requests or if
you want to add some extra headers. As you can see, HTTPS connections
are also supported (using ssl_client). */
struct http_request *http_dorequest( char *host, int port, int ssl, char *request, http_input_function func, gpointer data );
struct http_request *http_dorequest_url( char *url_string, http_input_function func, gpointer data );
|