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

Comparing AnyEvent-HTTP/README (file contents):
Revision 1.14 by root, Fri Dec 31 03:47:32 2010 UTC vs.
Revision 1.27 by root, Sun Aug 28 09:31:29 2016 UTC

…		…
12	This module is an AnyEvent user, you need to make sure that you use and	12	This module is an AnyEvent user, you need to make sure that you use and
13	run a supported event loop.	13	run a supported event loop.
14		14
15	This module implements a simple, stateless and non-blocking HTTP client.	15	This module implements a simple, stateless and non-blocking HTTP client.
16	It supports GET, POST and other request methods, cookies and more, all	16	It supports GET, POST and other request methods, cookies and more, all
17	on a very low level. It can follow redirects supports proxies and	17	on a very low level. It can follow redirects, supports proxies, and
18	automatically limits the number of connections to the values specified	18	automatically limits the number of connections to the values specified
19	in the RFC.	19	in the RFC.
20		20
21	It should generally be a "good client" that is enough for most HTTP	21	It should generally be a "good client" that is enough for most HTTP
22	tasks. Simple tasks should be simple, but complex tasks should still be	22	tasks. Simple tasks should be simple, but complex tasks should still be
…		…
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 callback 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 occurred), 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" (uppercase to avoid clashing	59	response headers, the "pseudo-headers" (uppercase to avoid clashing
60	with possible response headers) "HTTPVersion", "Status" and "Reason"	60	with possible response headers) "HTTPVersion", "Status" and "Reason"
61	contain the three parts of the HTTP Status-Line of the same name. If	61	contain the three parts of the HTTP Status-Line of the same name. If
…		…
79	If the server sends a header multiple times, then their contents	79	If the server sends a header multiple times, then their contents
80	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.
81		81
82	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
83	hostname, then $data will be "undef", "$headers->{Status}" will be	83	hostname, then $data will be "undef", "$headers->{Status}" will be
84	"59x" (usually 599) and the "Reason" pseudo-header will contain an	84	590-599 and the "Reason" pseudo-header will contain an error
85	error message.	85	message. Currently the following status codes are used:
		86
		87	595 - errors during connection establishment, 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.).
86		93
87	A typical callback might look like this:	94	A typical callback might look like this:
88		95
89	sub {	96	sub {
90	my ($body, $hdr) = @_;	97	my ($body, $hdr) = @_;
…		…
99	Additional parameters are key-value pairs, and are fully optional.	106	Additional parameters are key-value pairs, and are fully optional.
100	They include:	107	They include:
101		108
102	recurse => $count (default: $MAX_RECURSE)	109	recurse => $count (default: $MAX_RECURSE)
103	Whether to recurse requests or not, e.g. on redirects,	110	Whether to recurse requests or not, e.g. on redirects,
104	authentication retries and so on, and how often to do so.	111	authentication and other retries and so on, and how often to do
		112	so.
		113
		114	Only redirects to http and https URLs are supported. While most
		115	common redirection forms are handled entirely within this
		116	module, some require the use of the optional URI module. If it
		117	is required but missing, then the request will fail with an
		118	error.
105		119
106	headers => hashref	120	headers => hashref
107	The request headers to use. Currently, "http_request" may	121	The request headers to use. Currently, "http_request" may
108	provide its own "Host:", "Content-Length:", "Connection:" and	122	provide its own "Host:", "Content-Length:", "Connection:" and
109	"Cookie:" headers and will provide defaults for "User-Agent:"	123	"Cookie:" headers and will provide defaults at least for "TE:",
110	and "Referer:" (this can be suppressed by using "undef" for	124	"Referer:" and "User-Agent:" (this can be suppressed by using
111	these headers in which case they won't be sent at all).	125	"undef" for these headers in which case they won't be sent at
		126	all).
		127
		128	You really should provide your own "User-Agent:" header value
		129	that is appropriate for your program - I wouldn't be surprised
		130	if the default AnyEvent string gets blocked by webservers sooner
		131	or later.
		132
		133	Also, make sure that your headers names and values do not
		134	contain any embedded newlines.
112		135
113	timeout => $seconds	136	timeout => $seconds
114	The time-out to use for various stages - each connect attempt	137	The time-out to use for various stages - each connect attempt
115	will reset the timeout, as will read or write activity, i.e.	138	will reset the timeout, as will read or write activity, i.e.
116	this is not an overall timeout.	139	this is not an overall timeout.
117		140
118	Default timeout is 5 minutes.	141	Default timeout is 5 minutes.
119		142
120	proxy => [$host, $port[, $scheme]] or undef	143	proxy => [$host, $port[, $scheme]] or undef
121	Use the given http proxy for all requests. If not specified,	144	Use the given http proxy for all requests, or no proxy if
122	then the default proxy (as specified by $ENV{http_proxy}) is	145	"undef" is used.
		146
		147	$scheme must be either missing or must be "http" for HTTP.
		148
		149	If not specified, then the default proxy is used (see
		150	"AnyEvent::HTTP::set_proxy").
		151
		152	Currently, if your proxy requires authorization, you have to
		153	specify an appropriate "Proxy-Authorization" header in every
123	used.	154	request.
124
125	$scheme must be either missing, "http" for HTTP or "https" for
126	HTTPS.
127		155
128	body => $string	156	body => $string
129	The request body, usually empty. Will be-sent as-is (future	157	The request body, usually empty. Will be sent as-is (future
130	versions of this module might offer more options).	158	versions of this module might offer more options).
131		159
132	cookie_jar => $hash_ref	160	cookie_jar => $hash_ref
133	Passing this parameter enables (simplified) cookie-processing,	161	Passing this parameter enables (simplified) cookie-processing,
134	loosely based on the original netscape specification.	162	loosely based on the original netscape specification.
135		163
136	The $hash_ref must be an (initially empty) hash reference which	164	The $hash_ref must be an (initially empty) hash reference which
137	will get updated automatically. It is possible to save the	165	will get updated automatically. It is possible to save the
138	cookie_jar to persistent storage with something like JSON or	166	cookie jar to persistent storage with something like JSON or
139	Storable, but this is not recommended, as expiry times are	167	Storable - see the "AnyEvent::HTTP::cookie_jar_expire" function
140	currently being ignored.	168	if you wish to remove expired or session-only cookies, and also
		169	for documentation on the format of the cookie jar.
141		170
142	Note that this cookie implementation is not of very high	171	Note that this cookie implementation is not meant to be
143	quality, nor meant to be complete. If you want complete cookie	172	complete. If you want complete cookie management you have to do
144	management you have to do that on your own. "cookie_jar" is	173	that on your own. "cookie_jar" is meant as a quick fix to get
145	meant as a quick fix to get some cookie-using sites working.	174	most cookie-using sites working. Cookies are a privacy disaster,
146	Cookies are a privacy disaster, do not use them unless required	175	do not use them unless required to.
147	to.	176
		177	When cookie processing is enabled, the "Cookie:" and
		178	"Set-Cookie:" headers will be set and handled by this module,
		179	otherwise they will be left untouched.
148		180
149	tls_ctx => $scheme \| $tls_ctx	181	tls_ctx => $scheme \| $tls_ctx
150	Specifies the AnyEvent::TLS context to be used for https	182	Specifies the AnyEvent::TLS context to be used for https
151	connections. This parameter follows the same rules as the	183	connections. This parameter follows the same rules as the
152	"tls_ctx" parameter to AnyEvent::Handle, but additionally, the	184	"tls_ctx" parameter to AnyEvent::Handle, but additionally, the
…		…
155	and high-security (CA and common-name verification) TLS context.	187	and high-security (CA and common-name verification) TLS context.
156		188
157	The default for this option is "low", which could be interpreted	189	The default for this option is "low", which could be interpreted
158	as "give me the page, no matter what".	190	as "give me the page, no matter what".
159		191
		192	See also the "sessionid" parameter.
		193
		194	session => $string
		195	The module might reuse connections to the same host internally.
		196	Sometimes (e.g. when using TLS), you do not want to reuse
		197	connections from other sessions. This can be achieved by setting
		198	this parameter to some unique ID (such as the address of an
		199	object storing your state data, or the TLS context) - only
		200	connections using the same unique ID will be reused.
		201
160	on_prepare => $callback->($fh)	202	on_prepare => $callback->($fh)
161	In rare cases you need to "tune" the socket before it is used to	203	In rare cases you need to "tune" the socket before it is used to
162	connect (for exmaple, to bind it on a given IP address). This	204	connect (for example, to bind it on a given IP address). This
163	parameter overrides the prepare callback passed to	205	parameter overrides the prepare callback passed to
164	"AnyEvent::Socket::tcp_connect" and behaves exactly the same way	206	"AnyEvent::Socket::tcp_connect" and behaves exactly the same way
165	(e.g. it has to provide a timeout). See the description for the	207	(e.g. it has to provide a timeout). See the description for the
166	$prepare_cb argument of "AnyEvent::Socket::tcp_connect" for	208	$prepare_cb argument of "AnyEvent::Socket::tcp_connect" for
167	details.	209	details.
…		…
192		234
193	This callback is useful, among other things, to quickly reject	235	This callback is useful, among other things, to quickly reject
194	unwanted content, which, if it is supposed to be rare, can be	236	unwanted content, which, if it is supposed to be rare, can be
195	faster than first doing a "HEAD" request.	237	faster than first doing a "HEAD" request.
196		238
		239	The downside is that cancelling the request makes it impossible
		240	to re-use the connection. Also, the "on_header" callback will
		241	not receive any trailer (headers sent after the response body).
		242
197	Example: cancel the request unless the content-type is	243	Example: cancel the request unless the content-type is
198	"text/html".	244	"text/html".
199		245
200	on_header => sub {	246	on_header => sub {
201	$_[0]{"content-type"} =~ /^text\/html\s*(?:;\|$)/	247	$_[0]{"content-type"} =~ /^text\/html\s*(?:;\|$)/
…		…
208		254
209	It has to return either true (in which case AnyEvent::HTTP will	255	It has to return either true (in which case AnyEvent::HTTP will
210	continue), or false, in which case AnyEvent::HTTP will cancel	256	continue), or false, in which case AnyEvent::HTTP will cancel
211	the download (and call the completion callback with an error	257	the download (and call the completion callback with an error
212	code of 598).	258	code of 598).
		259
		260	The downside to cancelling the request is that it makes it
		261	impossible to re-use the connection.
213		262
214	This callback is useful when the data is too large to be held in	263	This callback is useful when the data is too large to be held in
215	memory (so the callback writes it to a file) or when only some	264	memory (so the callback writes it to a file) or when only some
216	information should be extracted, or when the body should be	265	information should be extracted, or when the body should be
217	processed incrementally.	266	processed incrementally.
…		…
231	AnyEvent::Handle object associated with the connection. In error	280	AnyEvent::Handle object associated with the connection. In error
232	cases, "undef" will be passed. When there is no body (e.g.	281	cases, "undef" will be passed. When there is no body (e.g.
233	status 304), the empty string will be passed.	282	status 304), the empty string will be passed.
234		283
235	The handle object might or might not be in TLS mode, might be	284	The handle object might or might not be in TLS mode, might be
236	connected to a proxy, be a persistent connection etc., and	285	connected to a proxy, be a persistent connection, use chunked
237	configured in unspecified ways. The user is responsible for this	286	transfer encoding etc., and configured in unspecified ways. The
238	handle (it will not be used by this module anymore).	287	user is responsible for this handle (it will not be used by this
		288	module anymore).
239		289
240	This is useful with some push-type services, where, after the	290	This is useful with some push-type services, where, after the
241	initial headers, an interactive protocol is used (typical	291	initial headers, an interactive protocol is used (typical
242	example would be the push-style twitter API which starts a	292	example would be the push-style twitter API which starts a
243	JSON/XML stream).	293	JSON/XML stream).
244		294
245	If you think you need this, first have a look at "on_body", to	295	If you think you need this, first have a look at "on_body", to
246	see if that doesn't solve your problem in a better way.	296	see if that doesn't solve your problem in a better way.
247		297
		298	persistent => $boolean
		299	Try to create/reuse a persistent connection. When this flag is
		300	set (default: true for idempotent requests, false for all
		301	others), then "http_request" tries to re-use an existing
		302	(previously-created) persistent connection to the host and,
		303	failing that, tries to create a new one.
		304
		305	Requests failing in certain ways will be automatically retried
		306	once, which is dangerous for non-idempotent requests, which is
		307	why it defaults to off for them. The reason for this is because
		308	the bozos who designed HTTP/1.1 made it impossible to
		309	distinguish between a fatal error and a normal connection
		310	timeout, so you never know whether there was a problem with your
		311	request or not.
		312
		313	When reusing an existent connection, many parameters (such as
		314	TLS context) will be ignored. See the "session" parameter for a
		315	workaround.
		316
		317	keepalive => $boolean
		318	Only used when "persistent" is also true. This parameter decides
		319	whether "http_request" tries to handshake a HTTP/1.0-style
		320	keep-alive connection (as opposed to only a HTTP/1.1 persistent
		321	connection).
		322
		323	The default is true, except when using a proxy, in which case it
		324	defaults to false, as HTTP/1.0 proxies cannot support this in a
		325	meaningful way.
		326
		327	handle_params => { key => value ... }
		328	The key-value pairs in this hash will be passed to any
		329	AnyEvent::Handle constructor that is called - not all requests
		330	will create a handle, and sometimes more than one is created, so
		331	this parameter is only good for setting hints.
		332
		333	Example: set the maximum read size to 4096, to potentially
		334	conserve memory at the cost of speed.
		335
		336	handle_params => {
		337	max_read_size => 4096,
		338	},
		339
248	Example: make a simple HTTP GET request for http://www.nethype.de/	340	Example: do a simple HTTP GET request for http://www.nethype.de/ and
		341	print the response body.
249		342
250	http_request GET => "http://www.nethype.de/", sub {	343	http_request GET => "http://www.nethype.de/", sub {
251	my ($body, $hdr) = @_;	344	my ($body, $hdr) = @_;
252	print "$body\n";	345	print "$body\n";
253	};	346	};
254		347
255	Example: make a HTTP HEAD request on https://www.google.com/, use a	348	Example: do a HTTP HEAD request on https://www.google.com/, use a
256	timeout of 30 seconds.	349	timeout of 30 seconds.
257		350
258	http_request	351	http_request
259	GET => "https://www.google.com",	352	HEAD => "https://www.google.com",
		353	headers => { "user-agent" => "MySearchClient 1.0" },
260	timeout => 30,	354	timeout => 30,
261	sub {	355	sub {
262	my ($body, $hdr) = @_;	356	my ($body, $hdr) = @_;
263	use Data::Dumper;	357	use Data::Dumper;
264	print Dumper $hdr;	358	print Dumper $hdr;
265	}	359	}
266	;	360	;
267		361
268	Example: make another simple HTTP GET request, but immediately try	362	Example: do another simple HTTP GET request, but immediately try to
269	to cancel it.	363	cancel it.
270		364
271	my $request = http_request GET => "http://www.nethype.de/", sub {	365	my $request = http_request GET => "http://www.nethype.de/", sub {
272	my ($body, $hdr) = @_;	366	my ($body, $hdr) = @_;
273	print "$body\n";	367	print "$body\n";
274	};	368	};
…		…
279	AnyEvent::HTTP uses the AnyEvent::Socket::tcp_connect function for the	373	AnyEvent::HTTP uses the AnyEvent::Socket::tcp_connect function for the
280	actual connection, which in turn uses AnyEvent::DNS to resolve	374	actual connection, which in turn uses AnyEvent::DNS to resolve
281	hostnames. The latter is a simple stub resolver and does no caching on	375	hostnames. The latter is a simple stub resolver and does no caching on
282	its own. If you want DNS caching, you currently have to provide your own	376	its own. If you want DNS caching, you currently have to provide your own
283	default resolver (by storing a suitable resolver object in	377	default resolver (by storing a suitable resolver object in
284	$AnyEvent::DNS::RESOLVER).	378	$AnyEvent::DNS::RESOLVER) or your own "tcp_connect" callback.
285		379
286	GLOBAL FUNCTIONS AND VARIABLES	380	GLOBAL FUNCTIONS AND VARIABLES
287	AnyEvent::HTTP::set_proxy "proxy-url"	381	AnyEvent::HTTP::set_proxy "proxy-url"
288	Sets the default proxy server to use. The proxy-url must begin with	382	Sets the default proxy server to use. The proxy-url must begin with
289	a string of the form "http://host:port" (optionally "https:..."),	383	a string of the form "http://host:port", croaks otherwise.
290	croaks otherwise.
291		384
292	To clear an already-set proxy, use "undef".	385	To clear an already-set proxy, use "undef".
		386
		387	When AnyEvent::HTTP is loaded for the first time it will query the
		388	default proxy from the operating system, currently by looking at
		389	"$ENV{http_proxy"}.
		390
		391	AnyEvent::HTTP::cookie_jar_expire $jar[, $session_end]
		392	Remove all cookies from the cookie jar that have been expired. If
		393	$session_end is given and true, then additionally remove all session
		394	cookies.
		395
		396	You should call this function (with a true $session_end) before you
		397	save cookies to disk, and you should call this function after
		398	loading them again. If you have a long-running program you can
		399	additionally call this function from time to time.
		400
		401	A cookie jar is initially an empty hash-reference that is managed by
		402	this module. Its format is subject to change, but currently it is as
		403	follows:
		404
		405	The key "version" has to contain 1, otherwise the hash gets emptied.
		406	All other keys are hostnames or IP addresses pointing to
		407	hash-references. The key for these inner hash references is the
		408	server path for which this cookie is meant, and the values are again
		409	hash-references. Each key of those hash-references is a cookie name,
		410	and the value, you guessed it, is another hash-reference, this time
		411	with the key-value pairs from the cookie, except for "expires" and
		412	"max-age", which have been replaced by a "_expires" key that
		413	contains the cookie expiry timestamp. Session cookies are indicated
		414	by not having an "_expires" key.
		415
		416	Here is an example of a cookie jar with a single cookie, so you have
		417	a chance of understanding the above paragraph:
		418
		419	{
		420	version => 1,
		421	"10.0.0.1" => {
		422	"/" => {
		423	"mythweb_id" => {
		424	_expires => 1293917923,
		425	value => "ooRung9dThee3ooyXooM1Ohm",
		426	},
		427	},
		428	},
		429	}
293		430
294	$date = AnyEvent::HTTP::format_date $timestamp	431	$date = AnyEvent::HTTP::format_date $timestamp
295	Takes a POSIX timestamp (seconds since the epoch) and formats it as	432	Takes a POSIX timestamp (seconds since the epoch) and formats it as
296	a HTTP Date (RFC 2616).	433	a HTTP Date (RFC 2616).
297		434
298	$timestamp = AnyEvent::HTTP::parse_date $date	435	$timestamp = AnyEvent::HTTP::parse_date $date
299	Takes a HTTP Date (RFC 2616) and returns the corresponding POSIX	436	Takes a HTTP Date (RFC 2616) or a Cookie date (netscape cookie spec)
		437	or a bunch of minor variations of those, and returns the
300	timestamp, or "undef" if the date cannot be parsed.	438	corresponding POSIX timestamp, or "undef" if the date cannot be
		439	parsed.
301		440
302	$AnyEvent::HTTP::MAX_RECURSE	441	$AnyEvent::HTTP::MAX_RECURSE
303	The default value for the "recurse" request parameter (default: 10).	442	The default value for the "recurse" request parameter (default: 10).
		443
		444	$AnyEvent::HTTP::TIMEOUT
		445	The default timeout for connection operations (default: 300).
304		446
305	$AnyEvent::HTTP::USERAGENT	447	$AnyEvent::HTTP::USERAGENT
306	The default value for the "User-Agent" header (the default is	448	The default value for the "User-Agent" header (the default is
307	"Mozilla/5.0 (compatible; U; AnyEvent-HTTP/$VERSION;	449	"Mozilla/5.0 (compatible; U; AnyEvent-HTTP/$VERSION;
308	+http://software.schmorp.de/pkg/AnyEvent)").	450	+http://software.schmorp.de/pkg/AnyEvent)").
309		451
310	$AnyEvent::HTTP::MAX_PER_HOST	452	$AnyEvent::HTTP::MAX_PER_HOST
311	The maximum number of concurrent connections to the same host	453	The maximum number of concurrent connections to the same host
312	(identified by the hostname). If the limit is exceeded, then the	454	(identified by the hostname). If the limit is exceeded, then
313	additional requests are queued until previous connections are	455	additional requests are queued until previous connections are
314	closed.	456	closed. Both persistent and non-persistent connections are counted
		457	in this limit.
315		458
316	The default value for this is 4, and it is highly advisable to not	459	The default value for this is 4, and it is highly advisable to not
317	increase it.	460	increase it much.
		461
		462	For comparison: the RFC's recommend 4 non-persistent or 2 persistent
		463	connections, older browsers used 2, newer ones (such as firefox 3)
		464	typically use 6, and Opera uses 8 because like, they have the
		465	fastest browser and give a shit for everybody else on the planet.
		466
		467	$AnyEvent::HTTP::PERSISTENT_TIMEOUT
		468	The time after which idle persistent connections get closed by
		469	AnyEvent::HTTP (default: 3).
318		470
319	$AnyEvent::HTTP::ACTIVE	471	$AnyEvent::HTTP::ACTIVE
320	The number of active connections. This is not the number of	472	The number of active connections. This is not the number of
321	currently running requests, but the number of currently open and	473	currently running requests, but the number of currently open and
322	non-idle TCP connections. This number of can be useful for	474	non-idle TCP connections. This number can be useful for
323	load-leveling.	475	load-leveling.
324		476
		477	SHOWCASE
		478	This section contains some more elaborate "real-world" examples or code
		479	snippets.
		480
		481	HTTP/1.1 FILE DOWNLOAD
		482	Downloading files with HTTP can be quite tricky, especially when
		483	something goes wrong and you want to resume.
		484
		485	Here is a function that initiates and resumes a download. It uses the
		486	last modified time to check for file content changes, and works with
		487	many HTTP/1.0 servers as well, and usually falls back to a complete
		488	re-download on older servers.
		489
		490	It calls the completion callback with either "undef", which means a
		491	nonretryable error occurred, 0 when the download was partial and should
		492	be retried, and 1 if it was successful.
		493
		494	use AnyEvent::HTTP;
		495
		496	sub download($$$) {
		497	my ($url, $file, $cb) = @_;
		498
		499	open my $fh, "+<", $file
		500	or die "$file: $!";
		501
		502	my %hdr;
		503	my $ofs = 0;
		504
		505	if (stat $fh and -s _) {
		506	$ofs = -s _;
		507	warn "-s is ", $ofs;
		508	$hdr{"if-unmodified-since"} = AnyEvent::HTTP::format_date +(stat _)[9];
		509	$hdr{"range"} = "bytes=$ofs-";
		510	}
		511
		512	http_get $url,
		513	headers => \%hdr,
		514	on_header => sub {
		515	my ($hdr) = @_;
		516
		517	if ($hdr->{Status} == 200 && $ofs) {
		518	# resume failed
		519	truncate $fh, $ofs = 0;
		520	}
		521
		522	sysseek $fh, $ofs, 0;
		523
		524	1
		525	},
		526	on_body => sub {
		527	my ($data, $hdr) = @_;
		528
		529	if ($hdr->{Status} =~ /^2/) {
		530	length $data == syswrite $fh, $data
		531	or return; # abort on write errors
		532	}
		533
		534	1
		535	},
		536	sub {
		537	my (undef, $hdr) = @_;
		538
		539	my $status = $hdr->{Status};
		540
		541	if (my $time = AnyEvent::HTTP::parse_date $hdr->{"last-modified"}) {
		542	utime $time, $time, $fh;
		543	}
		544
		545	if ($status == 200 \|\| $status == 206 \|\| $status == 416) {
		546	# download ok \|\| resume ok \|\| file already fully downloaded
		547	$cb->(1, $hdr);
		548
		549	} elsif ($status == 412) {
		550	# file has changed while resuming, delete and retry
		551	unlink $file;
		552	$cb->(0, $hdr);
		553
		554	} elsif ($status == 500 or $status == 503 or $status =~ /^59/) {
		555	# retry later
		556	$cb->(0, $hdr);
		557
		558	} else {
		559	$cb->(undef, $hdr);
		560	}
		561	}
		562	;
		563	}
		564
		565	download "http://server/somelargefile", "/tmp/somelargefile", sub {
		566	if ($_[0]) {
		567	print "OK!\n";
		568	} elsif (defined $_[0]) {
		569	print "please retry later\n";
		570	} else {
		571	print "ERROR\n";
		572	}
		573	};
		574
325	SOCKS PROXIES	575	SOCKS PROXIES
326	Socks proxies are not directly supported by AnyEvent::HTTP. You can	576	Socks proxies are not directly supported by AnyEvent::HTTP. You can
327	compile your perl to support socks, or use an external program such as	577	compile your perl to support socks, or use an external program such as
328	socksify (dante) or tsocks to make your program use a socks proxy	578	socksify (dante) or tsocks to make your program use a socks proxy
329	transparently.	579	transparently.
330		580
…		…
382		632
383	AUTHOR	633	AUTHOR
384	Marc Lehmann <schmorp@schmorp.de>	634	Marc Lehmann <schmorp@schmorp.de>
385	http://home.schmorp.de/	635	http://home.schmorp.de/
386		636
387	With many thanks to Дмитрий Шалашов, who provided	637	With many thanks to Дмитрий Шалашов, who provided countless testcases
388	countless testcases and bugreports.	638	and bugreports.
389		639

Diff Legend

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

Comparing AnyEvent-HTTP/README (file contents): Revision 1.14 by root, Fri Dec 31 03:47:32 2010 UTC vs. Revision 1.27 by root, Sun Aug 28 09:31:29 2016 UTC

Diff Legend

Comparing AnyEvent-HTTP/README (file contents):
Revision 1.14 by root, Fri Dec 31 03:47:32 2010 UTC vs.
Revision 1.27 by root, Sun Aug 28 09:31:29 2016 UTC