[ViewVC] Diff of: cvs/AnyEvent-HTTP/README

Comparing AnyEvent-HTTP/README (file contents):
Revision 1.8 by root, Tue Jul 7 00:15:32 2009 UTC vs.
Revision 1.16 by root, Tue Jan 11 06:38:47 2011 UTC

…		…
46	URL must be an absolute http or https URL.	46	URL must be an absolute http or https URL.
47		47
48	When called in void context, nothing is returned. In other contexts,	48	When called in void context, nothing is returned. In other contexts,
49	"http_request" returns a "cancellation guard" - you have to keep the	49	"http_request" returns a "cancellation guard" - you have to keep the
50	object at least alive until the callback get called. If the object	50	object at least alive until the callback get called. If the object
51	gets destroyed before the callbakc is called, the request will be	51	gets destroyed before the callback is called, the request will be
52	cancelled.	52	cancelled.
53		53
54	The callback will be called with the response body data as first	54	The callback will be called with the response body data as first
55	argument (or "undef" if an error occured), and a hash-ref with	55	argument (or "undef" if an error occured), and a hash-ref with
56	response headers as second argument.	56	response headers (and trailers) as second argument.
57		57
58	All the headers in that hash are lowercased. In addition to the	58	All the headers in that hash are lowercased. In addition to the
59	response headers, the "pseudo-headers" "HTTPVersion", "Status" and	59	response headers, the "pseudo-headers" (uppercase to avoid clashing
		60	with possible response headers) "HTTPVersion", "Status" and "Reason"
60	"Reason" contain the three parts of the HTTP Status-Line of the same	61	contain the three parts of the HTTP Status-Line of the same name. If
		62	an error occurs during the body phase of a request, then the
		63	original "Status" and "Reason" values from the header are available
		64	as "OrigStatus" and "OrigReason".
		65
61	name. The pseudo-header "URL" contains the original URL (which can	66	The pseudo-header "URL" contains the actual URL (which can differ
62	differ from the requested URL when following redirects).	67	from the requested URL when following redirects - for example, you
		68	might get an error that your URL scheme is not supported even though
		69	your URL is a valid http URL because it redirected to an ftp URL, in
		70	which case you can look at the URL pseudo header).
		71
		72	The pseudo-header "Redirect" only exists when the request was a
		73	result of an internal redirect. In that case it is an array
		74	reference with the "($data, $headers)" from the redirect response.
		75	Note that this response could in turn be the result of a redirect
		76	itself, and "$headers->{Redirect}[1]{Redirect}" will then contain
		77	the original response, and so on.
63		78
64	If the server sends a header multiple times, then their contents	79	If the server sends a header multiple times, then their contents
65	will be joined together with a comma (","), as per the HTTP spec.	80	will be joined together with a comma (","), as per the HTTP spec.
66		81
67	If an internal error occurs, such as not being able to resolve a	82	If an internal error occurs, such as not being able to resolve a
68	hostname, then $data will be "undef", "$headers->{Status}" will be	83	hostname, then $data will be "undef", "$headers->{Status}" will be
69	"59x" (usually 599) and the "Reason" pseudo-header will contain an	84	590-599 and the "Reason" pseudo-header will contain an error
70	error message.	85	message. Currently the following status codes are used:
		86
		87	595 - errors during connection etsbalishment, proxy handshake.
		88	596 - errors during TLS negotiation, request sending and header
		89	processing.
		90	597 - errors during body receiving or processing.
		91	598 - user aborted request via "on_header" or "on_body".
		92	599 - other, usually nonretryable, errors (garbled URL etc.).
71		93
72	A typical callback might look like this:	94	A typical callback might look like this:
73		95
74	sub {	96	sub {
75	my ($body, $hdr) = @_;	97	my ($body, $hdr) = @_;
…		…
89	authentication retries and so on, and how often to do so.	111	authentication retries and so on, and how often to do so.
90		112
91	headers => hashref	113	headers => hashref
92	The request headers to use. Currently, "http_request" may	114	The request headers to use. Currently, "http_request" may
93	provide its own "Host:", "Content-Length:", "Connection:" and	115	provide its own "Host:", "Content-Length:", "Connection:" and
94	"Cookie:" headers and will provide defaults for "User-Agent:"	116	"Cookie:" headers and will provide defaults at least for "TE:",
95	and "Referer:".	117	"Referer:" and "User-Agent:" (this can be suppressed by using
		118	"undef" for these headers in which case they won't be sent at
		119	all).
		120
		121	You really should provide your own "User-Agent:" header value
		122	that is appropriate for your program - I wouldn't be surprised
		123	if the default AnyEvent string gets blocked by webservers sooner
		124	or later.
96		125
97	timeout => $seconds	126	timeout => $seconds
98	The time-out to use for various stages - each connect attempt	127	The time-out to use for various stages - each connect attempt
99	will reset the timeout, as will read or write activity. Default	128	will reset the timeout, as will read or write activity, i.e.
		129	this is not an overall timeout.
		130
100	timeout is 5 minutes.	131	Default timeout is 5 minutes.
101		132
102	proxy => [$host, $port[, $scheme]] or undef	133	proxy => [$host, $port[, $scheme]] or undef
103	Use the given http proxy for all requests. If not specified,	134	Use the given http proxy for all requests. If not specified,
104	then the default proxy (as specified by $ENV{http_proxy}) is	135	then the default proxy (as specified by $ENV{http_proxy}) is
105	used.	136	used.
106		137
107	$scheme must be either missing or "http" for HTTP, or "https"	138	$scheme must be either missing or must be "http" for HTTP.
108	for HTTPS.
109		139
110	body => $string	140	body => $string
111	The request body, usually empty. Will be-sent as-is (future	141	The request body, usually empty. Will be sent as-is (future
112	versions of this module might offer more options).	142	versions of this module might offer more options).
113		143
114	cookie_jar => $hash_ref	144	cookie_jar => $hash_ref
115	Passing this parameter enables (simplified) cookie-processing,	145	Passing this parameter enables (simplified) cookie-processing,
116	loosely based on the original netscape specification.	146	loosely based on the original netscape specification.
117		147
118	The $hash_ref must be an (initially empty) hash reference which	148	The $hash_ref must be an (initially empty) hash reference which
119	will get updated automatically. It is possible to save the	149	will get updated automatically. It is possible to save the
120	cookie_jar to persistent storage with something like JSON or	150	cookie jar to persistent storage with something like JSON or
121	Storable, but this is not recommended, as expiry times are	151	Storable - see the "AnyEvent::HTTP::cookie_jar_expire" function
122	currently being ignored.	152	if you wish to remove expired or session-only cookies, and also
		153	for documentation on the format of the cookie jar.
123		154
124	Note that this cookie implementation is not of very high	155	Note that this cookie implementation is not meant to be
125	quality, nor meant to be complete. If you want complete cookie	156	complete. If you want complete cookie management you have to do
126	management you have to do that on your own. "cookie_jar" is	157	that on your own. "cookie_jar" is meant as a quick fix to get
127	meant as a quick fix to get some cookie-using sites working.	158	most cookie-using sites working. Cookies are a privacy disaster,
128	Cookies are a privacy disaster, do not use them unless required	159	do not use them unless required to.
129	to.	160
		161	When cookie processing is enabled, the "Cookie:" and
		162	"Set-Cookie:" headers will be set and handled by this module,
		163	otherwise they will be left untouched.
130		164
131	tls_ctx => $scheme \| $tls_ctx	165	tls_ctx => $scheme \| $tls_ctx
132	Specifies the AnyEvent::TLS context to be used for https	166	Specifies the AnyEvent::TLS context to be used for https
133	connections. This parameter follows the same rules as the	167	connections. This parameter follows the same rules as the
134	"tls_ctx" parameter to AnyEvent::Handle, but additionally, the	168	"tls_ctx" parameter to AnyEvent::Handle, but additionally, the
…		…
137	and high-security (CA and common-name verification) TLS context.	171	and high-security (CA and common-name verification) TLS context.
138		172
139	The default for this option is "low", which could be interpreted	173	The default for this option is "low", which could be interpreted
140	as "give me the page, no matter what".	174	as "give me the page, no matter what".
141		175
		176	See also the "sessionid" parameter.
		177
		178	session => $string
		179	The module might reuse connections to the same host internally.
		180	Sometimes (e.g. when using TLS), you do not want to reuse
		181	connections from other sessions. This can be achieved by setting
		182	this parameter to some unique ID (such as the address of an
		183	object storing your state data, or the TLS context) - only
		184	connections using the same unique ID will be reused.
		185
		186	on_prepare => $callback->($fh)
		187	In rare cases you need to "tune" the socket before it is used to
		188	connect (for exmaple, to bind it on a given IP address). This
		189	parameter overrides the prepare callback passed to
		190	"AnyEvent::Socket::tcp_connect" and behaves exactly the same way
		191	(e.g. it has to provide a timeout). See the description for the
		192	$prepare_cb argument of "AnyEvent::Socket::tcp_connect" for
		193	details.
		194
		195	tcp_connect => $callback->($host, $service, $connect_cb,
		196	$prepare_cb)
		197	In even rarer cases you want total control over how
		198	AnyEvent::HTTP establishes connections. Normally it uses
		199	AnyEvent::Socket::tcp_connect to do this, but you can provide
		200	your own "tcp_connect" function - obviously, it has to follow
		201	the same calling conventions, except that it may always return a
		202	connection guard object.
		203
		204	There are probably lots of weird uses for this function,
		205	starting from tracing the hosts "http_request" actually tries to
		206	connect, to (inexact but fast) host => IP address caching or
		207	even socks protocol support.
		208
142	on_header => $callback->($headers)	209	on_header => $callback->($headers)
143	When specified, this callback will be called with the header	210	When specified, this callback will be called with the header
144	hash as soon as headers have been successfully received from the	211	hash as soon as headers have been successfully received from the
145	remote server (not on locally-generated errors).	212	remote server (not on locally-generated errors).
146		213
…		…
151		218
152	This callback is useful, among other things, to quickly reject	219	This callback is useful, among other things, to quickly reject
153	unwanted content, which, if it is supposed to be rare, can be	220	unwanted content, which, if it is supposed to be rare, can be
154	faster than first doing a "HEAD" request.	221	faster than first doing a "HEAD" request.
155		222
		223	The downside is that cancelling the request makes it impossible
		224	to re-use the connection. Also, the "on_header" callback will
		225	not receive any trailer (headers sent after the response body).
		226
156	Example: cancel the request unless the content-type is	227	Example: cancel the request unless the content-type is
157	"text/html".	228	"text/html".
158		229
159	on_header => sub {	230	on_header => sub {
160	$_[0]{"content-type"} =~ /^text\/html\s*(?:;\|$)/	231	$_[0]{"content-type"} =~ /^text\/html\s*(?:;\|$)/
…		…
168	It has to return either true (in which case AnyEvent::HTTP will	239	It has to return either true (in which case AnyEvent::HTTP will
169	continue), or false, in which case AnyEvent::HTTP will cancel	240	continue), or false, in which case AnyEvent::HTTP will cancel
170	the download (and call the completion callback with an error	241	the download (and call the completion callback with an error
171	code of 598).	242	code of 598).
172		243
		244	The downside to cancelling the request is that it makes it
		245	impossible to re-use the connection.
		246
173	This callback is useful when the data is too large to be held in	247	This callback is useful when the data is too large to be held in
174	memory (so the callback writes it to a file) or when only some	248	memory (so the callback writes it to a file) or when only some
175	information should be extracted, or when the body should be	249	information should be extracted, or when the body should be
176	processed incrementally.	250	processed incrementally.
177		251
178	It is usually preferred over doing your own body handling via	252	It is usually preferred over doing your own body handling via
179	"want_body_handle".	253	"want_body_handle", but in case of streaming APIs, where HTTP is
		254	only used to create a connection, "want_body_handle" is the
		255	better alternative, as it allows you to install your own event
		256	handler, reducing resource usage.
180		257
181	want_body_handle => $enable	258	want_body_handle => $enable
182	When enabled (default is disabled), the behaviour of	259	When enabled (default is disabled), the behaviour of
183	AnyEvent::HTTP changes considerably: after parsing the headers,	260	AnyEvent::HTTP changes considerably: after parsing the headers,
184	and instead of downloading the body (if any), the completion	261	and instead of downloading the body (if any), the completion
…		…
187	AnyEvent::Handle object associated with the connection. In error	264	AnyEvent::Handle object associated with the connection. In error
188	cases, "undef" will be passed. When there is no body (e.g.	265	cases, "undef" will be passed. When there is no body (e.g.
189	status 304), the empty string will be passed.	266	status 304), the empty string will be passed.
190		267
191	The handle object might or might not be in TLS mode, might be	268	The handle object might or might not be in TLS mode, might be
192	connected to a proxy, be a persistent connection etc., and	269	connected to a proxy, be a persistent connection, use chunked
193	configured in unspecified ways. The user is responsible for this	270	transfer encoding etc., and configured in unspecified ways. The
194	handle (it will not be used by this module anymore).	271	user is responsible for this handle (it will not be used by this
		272	module anymore).
195		273
196	This is useful with some push-type services, where, after the	274	This is useful with some push-type services, where, after the
197	initial headers, an interactive protocol is used (typical	275	initial headers, an interactive protocol is used (typical
198	example would be the push-style twitter API which starts a	276	example would be the push-style twitter API which starts a
199	JSON/XML stream).	277	JSON/XML stream).
200		278
201	If you think you need this, first have a look at "on_body", to	279	If you think you need this, first have a look at "on_body", to
202	see if that doesn'T solve your problem in a better way.	280	see if that doesn't solve your problem in a better way.
203		281
		282	persistent => $boolean
		283	Try to create/reuse a persistent connection. When this flag is
		284	set (default: true for idempotent requests, false for all
		285	others), then "http_request" tries to re-use an existing
		286	(previously-created) persistent connection to the host and,
		287	failing that, tries to create a new one.
		288
		289	Requests failing in certain ways will be automatically retried
		290	once, which is dangerous for non-idempotent requests, which is
		291	why it defaults to off for them. The reason for this is because
		292	the bozos who designed HTTP/1.1 made it impossible to
		293	distinguish between a fatal error and a normal connection
		294	timeout, so you never know whether there was a problem with your
		295	request or not.
		296
		297	When reusing an existent connection, many parameters (such as
		298	TLS context) will be ignored. See the "session" parameter for a
		299	workaround.
		300
		301	keepalive => $boolean
		302	Only used when "persistent" is also true. This parameter decides
		303	whether "http_request" tries to handshake a HTTP/1.0-style
		304	keep-alive connection (as opposed to only a HTTP/1.1 persistent
		305	connection).
		306
		307	The default is true, except when using a proxy, in which case it
		308	defaults to false, as HTTP/1.0 proxies cannot support this in a
		309	meaningful way.
		310
		311	handle_params => { key => value ... }
		312	The key-value pairs in this hash will be passed to any
		313	AnyEvent::Handle constructor that is called - not all requests
		314	will create a handle, and sometimes more than one is created, so
		315	this parameter is only good for setting hints.
		316
		317	Example: set the maximum read size to 4096, to potentially
		318	conserve memory at the cost of speed.
		319
		320	handle_params => {
		321	max_read_size => 4096,
		322	},
		323
204	Example: make a simple HTTP GET request for http://www.nethype.de/	324	Example: do a simple HTTP GET request for http://www.nethype.de/ and
		325	print the response body.
205		326
206	http_request GET => "http://www.nethype.de/", sub {	327	http_request GET => "http://www.nethype.de/", sub {
207	my ($body, $hdr) = @_;	328	my ($body, $hdr) = @_;
208	print "$body\n";	329	print "$body\n";
209	};	330	};
210		331
211	Example: make a HTTP HEAD request on https://www.google.com/, use a	332	Example: do a HTTP HEAD request on https://www.google.com/, use a
212	timeout of 30 seconds.	333	timeout of 30 seconds.
213		334
214	http_request	335	http_request
215	GET => "https://www.google.com",	336	GET => "https://www.google.com",
		337	headers => { "user-agent" => "MySearchClient 1.0" },
216	timeout => 30,	338	timeout => 30,
217	sub {	339	sub {
218	my ($body, $hdr) = @_;	340	my ($body, $hdr) = @_;
219	use Data::Dumper;	341	use Data::Dumper;
220	print Dumper $hdr;	342	print Dumper $hdr;
221	}	343	}
222	;	344	;
223		345
224	Example: make another simple HTTP GET request, but immediately try	346	Example: do another simple HTTP GET request, but immediately try to
225	to cancel it.	347	cancel it.
226		348
227	my $request = http_request GET => "http://www.nethype.de/", sub {	349	my $request = http_request GET => "http://www.nethype.de/", sub {
228	my ($body, $hdr) = @_;	350	my ($body, $hdr) = @_;
229	print "$body\n";	351	print "$body\n";
230	};	352	};
231		353
232	undef $request;	354	undef $request;
233		355
		356	DNS CACHING
		357	AnyEvent::HTTP uses the AnyEvent::Socket::tcp_connect function for the
		358	actual connection, which in turn uses AnyEvent::DNS to resolve
		359	hostnames. The latter is a simple stub resolver and does no caching on
		360	its own. If you want DNS caching, you currently have to provide your own
		361	default resolver (by storing a suitable resolver object in
		362	$AnyEvent::DNS::RESOLVER) or your own "tcp_connect" callback.
		363
234	GLOBAL FUNCTIONS AND VARIABLES	364	GLOBAL FUNCTIONS AND VARIABLES
235	AnyEvent::HTTP::set_proxy "proxy-url"	365	AnyEvent::HTTP::set_proxy "proxy-url"
236	Sets the default proxy server to use. The proxy-url must begin with	366	Sets the default proxy server to use. The proxy-url must begin with
237	a string of the form "http://host:port" (optionally "https:...").	367	a string of the form "http://host:port", croaks otherwise.
		368
		369	To clear an already-set proxy, use "undef".
		370
		371	AnyEvent::HTTP::cookie_jar_expire $jar[, $session_end]
		372	Remove all cookies from the cookie jar that have been expired. If
		373	$session_end is given and true, then additionally remove all session
		374	cookies.
		375
		376	You should call this function (with a true $session_end) before you
		377	save cookies to disk, and you should call this function after
		378	loading them again. If you have a long-running program you can
		379	additonally call this function from time to time.
		380
		381	A cookie jar is initially an empty hash-reference that is managed by
		382	this module. It's format is subject to change, but currently it is
		383	like this:
		384
		385	The key "version" has to contain 1, otherwise the hash gets emptied.
		386	All other keys are hostnames or IP addresses pointing to
		387	hash-references. The key for these inner hash references is the
		388	server path for which this cookie is meant, and the values are again
		389	hash-references. The keys of those hash-references is the cookie
		390	name, and the value, you guessed it, is another hash-reference, this
		391	time with the key-value pairs from the cookie, except for "expires"
		392	and "max-age", which have been replaced by a "_expires" key that
		393	contains the cookie expiry timestamp.
		394
		395	Here is an example of a cookie jar with a single cookie, so you have
		396	a chance of understanding the above paragraph:
		397
		398	{
		399	version => 1,
		400	"10.0.0.1" => {
		401	"/" => {
		402	"mythweb_id" => {
		403	_expires => 1293917923,
		404	value => "ooRung9dThee3ooyXooM1Ohm",
		405	},
		406	},
		407	},
		408	}
		409
		410	$date = AnyEvent::HTTP::format_date $timestamp
		411	Takes a POSIX timestamp (seconds since the epoch) and formats it as
		412	a HTTP Date (RFC 2616).
		413
		414	$timestamp = AnyEvent::HTTP::parse_date $date
		415	Takes a HTTP Date (RFC 2616) or a Cookie date (netscape cookie spec)
		416	or a bunch of minor variations of those, and returns the
		417	corresponding POSIX timestamp, or "undef" if the date cannot be
		418	parsed.
238		419
239	$AnyEvent::HTTP::MAX_RECURSE	420	$AnyEvent::HTTP::MAX_RECURSE
240	The default value for the "recurse" request parameter (default: 10).	421	The default value for the "recurse" request parameter (default: 10).
		422
		423	$AnyEvent::HTTP::TIMEOUT
		424	The default timeout for conenction operations (default: 300).
241		425
242	$AnyEvent::HTTP::USERAGENT	426	$AnyEvent::HTTP::USERAGENT
243	The default value for the "User-Agent" header (the default is	427	The default value for the "User-Agent" header (the default is
244	"Mozilla/5.0 (compatible; U; AnyEvent-HTTP/$VERSION;	428	"Mozilla/5.0 (compatible; U; AnyEvent-HTTP/$VERSION;
245	+http://software.schmorp.de/pkg/AnyEvent)").	429	+http://software.schmorp.de/pkg/AnyEvent)").
246		430
247	$AnyEvent::HTTP::MAX_PER_HOST	431	$AnyEvent::HTTP::MAX_PER_HOST
248	The maximum number of concurrent conenctions to the same host	432	The maximum number of concurrent connections to the same host
249	(identified by the hostname). If the limit is exceeded, then the	433	(identified by the hostname). If the limit is exceeded, then the
250	additional requests are queued until previous connections are	434	additional requests are queued until previous connections are
251	closed.	435	closed. Both persistent and non-persistent connections are counted
		436	in this limit.
252		437
253	The default value for this is 4, and it is highly advisable to not	438	The default value for this is 4, and it is highly advisable to not
254	increase it.	439	increase it much.
		440
		441	For comparison: the RFC's recommend 4 non-persistent or 2 persistent
		442	connections, older browsers used 2, newers (such as firefox 3)
		443	typically use 6, and Opera uses 8 because like, they have the
		444	fastest browser and give a shit for everybody else on the planet.
		445
		446	$AnyEvent::HTTP::PERSISTENT_TIMEOUT
		447	The time after which idle persistent conenctions get closed by
		448	AnyEvent::HTTP (default: 3).
255		449
256	$AnyEvent::HTTP::ACTIVE	450	$AnyEvent::HTTP::ACTIVE
257	The number of active connections. This is not the number of	451	The number of active connections. This is not the number of
258	currently running requests, but the number of currently open and	452	currently running requests, but the number of currently open and
259	non-idle TCP connections. This number of can be useful for	453	non-idle TCP connections. This number can be useful for
260	load-leveling.	454	load-leveling.
		455
		456	SHOWCASE
		457	This section contaisn some more elaborate "real-world" examples or code
		458	snippets.
		459
		460	HTTP/1.1 FILE DOWNLOAD
		461	Downloading files with HTTP cna be quite tricky, especially when
		462	something goes wrong and you want tor esume.
		463
		464	Here is a function that initiates and resumes a download. It uses the
		465	last modified time to check for file content changes, and works with
		466	many HTTP/1.0 servers as well, and usually falls back to a complete
		467	re-download on older servers.
		468
		469	It calls the completion callback with either "undef", which means a
		470	nonretryable error occured, 0 when the download was partial and should
		471	be retried, and 1 if it was successful.
		472
		473	use AnyEvent::HTTP;
		474
		475	sub download($$$) {
		476	my ($url, $file, $cb) = @_;
		477
		478	open my $fh, "+<", $file
		479	or die "$file: $!";
		480
		481	my %hdr;
		482	my $ofs = 0;
		483
		484	warn stat $fh;
		485	warn -s _;
		486	if (stat $fh and -s _) {
		487	$ofs = -s _;
		488	warn "-s is ", $ofs;#d#
		489	$hdr{"if-unmodified-since"} = AnyEvent::HTTP::format_date +(stat _)[9];
		490	$hdr{"range"} = "bytes=$ofs-";
		491	}
		492
		493	http_get $url,
		494	headers => \%hdr,
		495	on_header => sub {
		496	my ($hdr) = @_;
		497
		498	if ($hdr->{Status} == 200 && $ofs) {
		499	# resume failed
		500	truncate $fh, $ofs = 0;
		501	}
		502
		503	sysseek $fh, $ofs, 0;
		504
		505	1
		506	},
		507	on_body => sub {
		508	my ($data, $hdr) = @_;
		509
		510	if ($hdr->{Status} =~ /^2/) {
		511	length $data == syswrite $fh, $data
		512	or return; # abort on write errors
		513	}
		514
		515	1
		516	},
		517	sub {
		518	my (undef, $hdr) = @_;
		519
		520	my $status = $hdr->{Status};
		521
		522	if (my $time = AnyEvent::HTTP::parse_date $hdr->{"last-modified"}) {
		523	utime $fh, $time, $time;
		524	}
		525
		526	if ($status == 200 \|\| $status == 206 \|\| $status == 416) {
		527	# download ok \|\| resume ok \|\| file already fully downloaded
		528	$cb->(1, $hdr);
		529
		530	} elsif ($status == 412) {
		531	# file has changed while resuming, delete and retry
		532	unlink $file;
		533	$cb->(0, $hdr);
		534
		535	} elsif ($status == 500 or $status == 503 or $status =~ /^59/) {
		536	# retry later
		537	$cb->(0, $hdr);
		538
		539	} else {
		540	$cb->(undef, $hdr);
		541	}
		542	}
		543	;
		544	}
		545
		546	download "http://server/somelargefile", "/tmp/somelargefile", sub {
		547	if ($_[0]) {
		548	print "OK!\n";
		549	} elsif (defined $_[0]) {
		550	print "please retry later\n";
		551	} else {
		552	print "ERROR\n";
		553	}
		554	};
		555
		556	SOCKS PROXIES
		557	Socks proxies are not directly supported by AnyEvent::HTTP. You can
		558	compile your perl to support socks, or use an external program such as
		559	socksify (dante) or tsocks to make your program use a socks proxy
		560	transparently.
		561
		562	Alternatively, for AnyEvent::HTTP only, you can use your own
		563	"tcp_connect" function that does the proxy handshake - here is an
		564	example that works with socks4a proxies:
		565
		566	use Errno;
		567	use AnyEvent::Util;
		568	use AnyEvent::Socket;
		569	use AnyEvent::Handle;
		570
		571	# host, port and username of/for your socks4a proxy
		572	my $socks_host = "10.0.0.23";
		573	my $socks_port = 9050;
		574	my $socks_user = "";
		575
		576	sub socks4a_connect {
		577	my ($host, $port, $connect_cb, $prepare_cb) = @_;
		578
		579	my $hdl = new AnyEvent::Handle
		580	connect => [$socks_host, $socks_port],
		581	on_prepare => sub { $prepare_cb->($_[0]{fh}) },
		582	on_error => sub { $connect_cb->() },
		583	;
		584
		585	$hdl->push_write (pack "CCnNZZ", 4, 1, $port, 1, $socks_user, $host);
		586
		587	$hdl->push_read (chunk => 8, sub {
		588	my ($hdl, $chunk) = @_;
		589	my ($status, $port, $ipn) = unpack "xCna4", $chunk;
		590
		591	if ($status == 0x5a) {
		592	$connect_cb->($hdl->{fh}, (format_address $ipn) . ":$port");
		593	} else {
		594	$! = Errno::ENXIO; $connect_cb->();
		595	}
		596	});
		597
		598	$hdl
		599	}
		600
		601	Use "socks4a_connect" instead of "tcp_connect" when doing
		602	"http_request"s, possibly after switching off other proxy types:
		603
		604	AnyEvent::HTTP::set_proxy undef; # usually you do not want other proxies
		605
		606	http_get 'http://www.google.com', tcp_connect => \&socks4a_connect, sub {
		607	my ($data, $headers) = @_;
		608	...
		609	};
261		610
262	SEE ALSO	611	SEE ALSO
263	AnyEvent.	612	AnyEvent.
264		613
265	AUTHOR	614	AUTHOR

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing AnyEvent-HTTP/README (file contents): Revision 1.8 by root, Tue Jul 7 00:15:32 2009 UTC vs. Revision 1.16 by root, Tue Jan 11 06:38:47 2011 UTC

Diff Legend

Comparing AnyEvent-HTTP/README (file contents):
Revision 1.8 by root, Tue Jul 7 00:15:32 2009 UTC vs.
Revision 1.16 by root, Tue Jan 11 06:38:47 2011 UTC