ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent/lib/AnyEvent/Handle.pm
(Generate patch)

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents):
Revision 1.84 by root, Thu Aug 21 19:13:05 2008 UTC vs.
Revision 1.219 by root, Mon Jul 18 01:19:43 2011 UTC

1package AnyEvent::Handle;
2
3no warnings;
4use strict qw(subs vars);
5
6use AnyEvent ();
7use AnyEvent::Util qw(WSAEWOULDBLOCK);
8use Scalar::Util ();
9use Carp ();
10use Fcntl ();
11use Errno qw(EAGAIN EINTR);
12
13=head1 NAME 1=head1 NAME
14 2
15AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent 3AnyEvent::Handle - non-blocking I/O on streaming handles via AnyEvent
16
17=cut
18
19our $VERSION = 4.232;
20 4
21=head1 SYNOPSIS 5=head1 SYNOPSIS
22 6
23 use AnyEvent; 7 use AnyEvent;
24 use AnyEvent::Handle; 8 use AnyEvent::Handle;
25 9
26 my $cv = AnyEvent->condvar; 10 my $cv = AnyEvent->condvar;
27 11
28 my $handle = 12 my $hdl; $hdl = new AnyEvent::Handle
29 AnyEvent::Handle->new (
30 fh => \*STDIN, 13 fh => \*STDIN,
31 on_eof => sub { 14 on_error => sub {
32 $cv->broadcast; 15 my ($hdl, $fatal, $msg) = @_;
33 }, 16 warn "got error $msg\n";
17 $hdl->destroy;
18 $cv->send;
34 ); 19 };
35 20
36 # send some request line 21 # send some request line
37 $handle->push_write ("getinfo\015\012"); 22 $hdl->push_write ("getinfo\015\012");
38 23
39 # read the response line 24 # read the response line
40 $handle->push_read (line => sub { 25 $hdl->push_read (line => sub {
41 my ($handle, $line) = @_; 26 my ($hdl, $line) = @_;
42 warn "read line <$line>\n"; 27 warn "got line <$line>\n";
43 $cv->send; 28 $cv->send;
44 }); 29 });
45 30
46 $cv->recv; 31 $cv->recv;
47 32
48=head1 DESCRIPTION 33=head1 DESCRIPTION
49 34
50This module is a helper module to make it easier to do event-based I/O on 35This is a helper module to make it easier to do event-based I/O on
51filehandles. For utility functions for doing non-blocking connects and accepts 36stream-based filehandles (sockets, pipes, and other stream things).
52on sockets see L<AnyEvent::Util>.
53 37
54The L<AnyEvent::Intro> tutorial contains some well-documented 38The L<AnyEvent::Intro> tutorial contains some well-documented
55AnyEvent::Handle examples. 39AnyEvent::Handle examples.
56 40
57In the following, when the documentation refers to of "bytes" then this 41In the following, where the documentation refers to "bytes", it means
58means characters. As sysread and syswrite are used for all I/O, their 42characters. As sysread and syswrite are used for all I/O, their
59treatment of characters applies to this module as well. 43treatment of characters applies to this module as well.
44
45At the very minimum, you should specify C<fh> or C<connect>, and the
46C<on_error> callback.
60 47
61All callbacks will be invoked with the handle object as their first 48All callbacks will be invoked with the handle object as their first
62argument. 49argument.
63 50
51=cut
52
53package AnyEvent::Handle;
54
55use Scalar::Util ();
56use List::Util ();
57use Carp ();
58use Errno qw(EAGAIN EINTR);
59
60use AnyEvent (); BEGIN { AnyEvent::common_sense }
61use AnyEvent::Util qw(WSAEWOULDBLOCK);
62
63our $VERSION = $AnyEvent::VERSION;
64
65sub _load_func($) {
66 my $func = $_[0];
67
68 unless (defined &$func) {
69 my $pkg = $func;
70 do {
71 $pkg =~ s/::[^:]+$//
72 or return;
73 eval "require $pkg";
74 } until defined &$func;
75 }
76
77 \&$func
78}
79
80sub MAX_READ_SIZE() { 131072 }
81
64=head1 METHODS 82=head1 METHODS
65 83
66=over 4 84=over 4
67 85
68=item B<new (%args)> 86=item $handle = B<new> AnyEvent::Handle fh => $filehandle, key => value...
69 87
70The constructor supports these arguments (all as key => value pairs). 88The constructor supports these arguments (all as C<< key => value >> pairs).
71 89
72=over 4 90=over 4
73 91
74=item fh => $filehandle [MANDATORY] 92=item fh => $filehandle [C<fh> or C<connect> MANDATORY]
75 93
76The filehandle this L<AnyEvent::Handle> object will operate on. 94The filehandle this L<AnyEvent::Handle> object will operate on.
77
78NOTE: The filehandle will be set to non-blocking mode (using 95NOTE: The filehandle will be set to non-blocking mode (using
79C<AnyEvent::Util::fh_nonblocking>) by the constructor and needs to stay in 96C<AnyEvent::Util::fh_nonblocking>) by the constructor and needs to stay in
80that mode. 97that mode.
81 98
99=item connect => [$host, $service] [C<fh> or C<connect> MANDATORY]
100
101Try to connect to the specified host and service (port), using
102C<AnyEvent::Socket::tcp_connect>. The C<$host> additionally becomes the
103default C<peername>.
104
105You have to specify either this parameter, or C<fh>, above.
106
107It is possible to push requests on the read and write queues, and modify
108properties of the stream, even while AnyEvent::Handle is connecting.
109
110When this parameter is specified, then the C<on_prepare>,
111C<on_connect_error> and C<on_connect> callbacks will be called under the
112appropriate circumstances:
113
114=over 4
115
82=item on_eof => $cb->($handle) 116=item on_prepare => $cb->($handle)
83 117
84Set the callback to be called when an end-of-file condition is detected, 118This (rarely used) callback is called before a new connection is
85i.e. in the case of a socket, when the other side has closed the 119attempted, but after the file handle has been created (you can access that
86connection cleanly. 120file handle via C<< $handle->{fh} >>). It could be used to prepare the
121file handle with parameters required for the actual connect (as opposed to
122settings that can be changed when the connection is already established).
87 123
88For sockets, this just means that the other side has stopped sending data, 124The return value of this callback should be the connect timeout value in
89you can still try to write data, and, in fact, one can return from the eof 125seconds (or C<0>, or C<undef>, or the empty list, to indicate that the
90callback and continue writing data, as only the read part has been shut 126default timeout is to be used).
91down.
92 127
93While not mandatory, it is I<highly> recommended to set an eof callback, 128=item on_connect => $cb->($handle, $host, $port, $retry->())
94otherwise you might end up with a closed socket while you are still
95waiting for data.
96 129
97If an EOF condition has been detected but no C<on_eof> callback has been 130This callback is called when a connection has been successfully established.
98set, then a fatal error will be raised with C<$!> set to <0>.
99 131
132The peer's numeric host and port (the socket peername) are passed as
133parameters, together with a retry callback.
134
135If, for some reason, the handle is not acceptable, calling C<$retry>
136will continue with the next connection target (in case of multi-homed
137hosts or SRV records there can be multiple connection endpoints). At the
138time it is called the read and write queues, eof status, tls status and
139similar properties of the handle will have been reset.
140
141In most cases, you should ignore the C<$retry> parameter.
142
143=item on_connect_error => $cb->($handle, $message)
144
145This callback is called when the connection could not be
146established. C<$!> will contain the relevant error code, and C<$message> a
147message describing it (usually the same as C<"$!">).
148
149If this callback isn't specified, then C<on_error> will be called with a
150fatal error instead.
151
152=back
153
100=item on_error => $cb->($handle, $fatal) 154=item on_error => $cb->($handle, $fatal, $message)
101 155
102This is the error callback, which is called when, well, some error 156This is the error callback, which is called when, well, some error
103occured, such as not being able to resolve the hostname, failure to 157occured, such as not being able to resolve the hostname, failure to
104connect or a read error. 158connect, or a read error.
105 159
106Some errors are fatal (which is indicated by C<$fatal> being true). On 160Some errors are fatal (which is indicated by C<$fatal> being true). On
107fatal errors the handle object will be shut down and will not be usable 161fatal errors the handle object will be destroyed (by a call to C<< ->
108(but you are free to look at the current C< ->rbuf >). Examples of fatal 162destroy >>) after invoking the error callback (which means you are free to
109errors are an EOF condition with active (but unsatisifable) read watchers 163examine the handle object). Examples of fatal errors are an EOF condition
110(C<EPIPE>) or I/O errors. 164with active (but unsatisfiable) read watchers (C<EPIPE>) or I/O errors. In
165cases where the other side can close the connection at will, it is
166often easiest to not report C<EPIPE> errors in this callback.
111 167
168AnyEvent::Handle tries to find an appropriate error code for you to check
169against, but in some cases (TLS errors), this does not work well. It is
170recommended to always output the C<$message> argument in human-readable
171error messages (it's usually the same as C<"$!">).
172
112Non-fatal errors can be retried by simply returning, but it is recommended 173Non-fatal errors can be retried by returning, but it is recommended
113to simply ignore this parameter and instead abondon the handle object 174to simply ignore this parameter and instead abondon the handle object
114when this callback is invoked. Examples of non-fatal errors are timeouts 175when this callback is invoked. Examples of non-fatal errors are timeouts
115C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>). 176C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
116 177
117On callback entrance, the value of C<$!> contains the operating system 178On entry to the callback, the value of C<$!> contains the operating
118error (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT> or C<EBADMSG>). 179system error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or
180C<EPROTO>).
119 181
120While not mandatory, it is I<highly> recommended to set this callback, as 182While not mandatory, it is I<highly> recommended to set this callback, as
121you will not be notified of errors otherwise. The default simply calls 183you will not be notified of errors otherwise. The default just calls
122C<croak>. 184C<croak>.
123 185
124=item on_read => $cb->($handle) 186=item on_read => $cb->($handle)
125 187
126This sets the default read callback, which is called when data arrives 188This sets the default read callback, which is called when data arrives
127and no read request is in the queue (unlike read queue callbacks, this 189and no read request is in the queue (unlike read queue callbacks, this
128callback will only be called when at least one octet of data is in the 190callback will only be called when at least one octet of data is in the
129read buffer). 191read buffer).
130 192
131To access (and remove data from) the read buffer, use the C<< ->rbuf >> 193To access (and remove data from) the read buffer, use the C<< ->rbuf >>
132method or access the C<$handle->{rbuf}> member directly. 194method or access the C<< $handle->{rbuf} >> member directly. Note that you
195must not enlarge or modify the read buffer, you can only remove data at
196the beginning from it.
133 197
198You can also call C<< ->push_read (...) >> or any other function that
199modifies the read queue. Or do both. Or ...
200
134When an EOF condition is detected then AnyEvent::Handle will first try to 201When an EOF condition is detected, AnyEvent::Handle will first try to
135feed all the remaining data to the queued callbacks and C<on_read> before 202feed all the remaining data to the queued callbacks and C<on_read> before
136calling the C<on_eof> callback. If no progress can be made, then a fatal 203calling the C<on_eof> callback. If no progress can be made, then a fatal
137error will be raised (with C<$!> set to C<EPIPE>). 204error will be raised (with C<$!> set to C<EPIPE>).
138 205
206Note that, unlike requests in the read queue, an C<on_read> callback
207doesn't mean you I<require> some data: if there is an EOF and there
208are outstanding read requests then an error will be flagged. With an
209C<on_read> callback, the C<on_eof> callback will be invoked.
210
211=item on_eof => $cb->($handle)
212
213Set the callback to be called when an end-of-file condition is detected,
214i.e. in the case of a socket, when the other side has closed the
215connection cleanly, and there are no outstanding read requests in the
216queue (if there are read requests, then an EOF counts as an unexpected
217connection close and will be flagged as an error).
218
219For sockets, this just means that the other side has stopped sending data,
220you can still try to write data, and, in fact, one can return from the EOF
221callback and continue writing data, as only the read part has been shut
222down.
223
224If an EOF condition has been detected but no C<on_eof> callback has been
225set, then a fatal error will be raised with C<$!> set to <0>.
226
139=item on_drain => $cb->($handle) 227=item on_drain => $cb->($handle)
140 228
141This sets the callback that is called when the write buffer becomes empty 229This sets the callback that is called when the write buffer becomes empty
142(or when the callback is set and the buffer is empty already). 230(or immediately if the buffer is empty already).
143 231
144To append to the write buffer, use the C<< ->push_write >> method. 232To append to the write buffer, use the C<< ->push_write >> method.
145 233
146This callback is useful when you don't want to put all of your write data 234This callback is useful when you don't want to put all of your write data
147into the queue at once, for example, when you want to write the contents 235into the queue at once, for example, when you want to write the contents
149memory and push it into the queue, but instead only read more data from 237memory and push it into the queue, but instead only read more data from
150the file when the write queue becomes empty. 238the file when the write queue becomes empty.
151 239
152=item timeout => $fractional_seconds 240=item timeout => $fractional_seconds
153 241
242=item rtimeout => $fractional_seconds
243
244=item wtimeout => $fractional_seconds
245
154If non-zero, then this enables an "inactivity" timeout: whenever this many 246If non-zero, then these enables an "inactivity" timeout: whenever this
155seconds pass without a successful read or write on the underlying file 247many seconds pass without a successful read or write on the underlying
156handle, the C<on_timeout> callback will be invoked (and if that one is 248file handle (or a call to C<timeout_reset>), the C<on_timeout> callback
157missing, an C<ETIMEDOUT> error will be raised). 249will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT>
250error will be raised).
158 251
252There are three variants of the timeouts that work independently of each
253other, for both read and write (triggered when nothing was read I<OR>
254written), just read (triggered when nothing was read), and just write:
255C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks
256C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions
257C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>.
258
159Note that timeout processing is also active when you currently do not have 259Note that timeout processing is active even when you do not have any
160any outstanding read or write requests: If you plan to keep the connection 260outstanding read or write requests: If you plan to keep the connection
161idle then you should disable the timout temporarily or ignore the timeout 261idle then you should disable the timeout temporarily or ignore the
162in the C<on_timeout> callback. 262timeout in the corresponding C<on_timeout> callback, in which case
263AnyEvent::Handle will simply restart the timeout.
163 264
164Zero (the default) disables this timeout. 265Zero (the default) disables the corresponding timeout.
165 266
166=item on_timeout => $cb->($handle) 267=item on_timeout => $cb->($handle)
268
269=item on_rtimeout => $cb->($handle)
270
271=item on_wtimeout => $cb->($handle)
167 272
168Called whenever the inactivity timeout passes. If you return from this 273Called whenever the inactivity timeout passes. If you return from this
169callback, then the timeout will be reset as if some activity had happened, 274callback, then the timeout will be reset as if some activity had happened,
170so this condition is not fatal in any way. 275so this condition is not fatal in any way.
171 276
172=item rbuf_max => <bytes> 277=item rbuf_max => <bytes>
173 278
174If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>) 279If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>)
175when the read buffer ever (strictly) exceeds this size. This is useful to 280when the read buffer ever (strictly) exceeds this size. This is useful to
176avoid denial-of-service attacks. 281avoid some forms of denial-of-service attacks.
177 282
178For example, a server accepting connections from untrusted sources should 283For example, a server accepting connections from untrusted sources should
179be configured to accept only so-and-so much data that it cannot act on 284be configured to accept only so-and-so much data that it cannot act on
180(for example, when expecting a line, an attacker could send an unlimited 285(for example, when expecting a line, an attacker could send an unlimited
181amount of data without a callback ever being called as long as the line 286amount of data without a callback ever being called as long as the line
182isn't finished). 287isn't finished).
183 288
289=item wbuf_max => <bytes>
290
291If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>)
292when the write buffer ever (strictly) exceeds this size. This is useful to
293avoid some forms of denial-of-service attacks.
294
295Although the units of this parameter is bytes, this is the I<raw> number
296of bytes not yet accepted by the kernel. This can make a difference when
297you e.g. use TLS, as TLS typically makes your write data larger (but it
298can also make it smaller due to compression).
299
300As an example of when this limit is useful, take a chat server that sends
301chat messages to a client. If the client does not read those in a timely
302manner then the send buffer in the server would grow unbounded.
303
184=item autocork => <boolean> 304=item autocork => <boolean>
185 305
186When disabled (the default), then C<push_write> will try to immediately 306When disabled (the default), C<push_write> will try to immediately
187write the data to the handle if possible. This avoids having to register 307write the data to the handle if possible. This avoids having to register
188a write watcher and wait for the next event loop iteration, but can be 308a write watcher and wait for the next event loop iteration, but can
189inefficient if you write multiple small chunks (this disadvantage is 309be inefficient if you write multiple small chunks (on the wire, this
190usually avoided by your kernel's nagle algorithm, see C<low_delay>). 310disadvantage is usually avoided by your kernel's nagle algorithm, see
311C<no_delay>, but this option can save costly syscalls).
191 312
192When enabled, then writes will always be queued till the next event loop 313When enabled, writes will always be queued till the next event loop
193iteration. This is efficient when you do many small writes per iteration, 314iteration. This is efficient when you do many small writes per iteration,
194but less efficient when you do a single write only. 315but less efficient when you do a single write only per iteration (or when
316the write buffer often is full). It also increases write latency.
195 317
196=item no_delay => <boolean> 318=item no_delay => <boolean>
197 319
198When doing small writes on sockets, your operating system kernel might 320When doing small writes on sockets, your operating system kernel might
199wait a bit for more data before actually sending it out. This is called 321wait a bit for more data before actually sending it out. This is called
200the Nagle algorithm, and usually it is beneficial. 322the Nagle algorithm, and usually it is beneficial.
201 323
202In some situations you want as low a delay as possible, which cna be 324In some situations you want as low a delay as possible, which can be
203accomplishd by setting this option to true. 325accomplishd by setting this option to a true value.
204 326
205The default is your opertaing system's default behaviour, this option 327The default is your operating system's default behaviour (most likely
206explicitly enables or disables it, if possible. 328enabled). This option explicitly enables or disables it, if possible.
329
330=item keepalive => <boolean>
331
332Enables (default disable) the SO_KEEPALIVE option on the stream socket:
333normally, TCP connections have no time-out once established, so TCP
334connections, once established, can stay alive forever even when the other
335side has long gone. TCP keepalives are a cheap way to take down long-lived
336TCP connections when the other side becomes unreachable. While the default
337is OS-dependent, TCP keepalives usually kick in after around two hours,
338and, if the other side doesn't reply, take down the TCP connection some 10
339to 15 minutes later.
340
341It is harmless to specify this option for file handles that do not support
342keepalives, and enabling it on connections that are potentially long-lived
343is usually a good idea.
344
345=item oobinline => <boolean>
346
347BSD majorly fucked up the implementation of TCP urgent data. The result
348is that almost no OS implements TCP according to the specs, and every OS
349implements it slightly differently.
350
351If you want to handle TCP urgent data, then setting this flag (the default
352is enabled) gives you the most portable way of getting urgent data, by
353putting it into the stream.
354
355Since BSD emulation of OOB data on top of TCP's urgent data can have
356security implications, AnyEvent::Handle sets this flag automatically
357unless explicitly specified. Note that setting this flag after
358establishing a connection I<may> be a bit too late (data loss could
359already have occured on BSD systems), but at least it will protect you
360from most attacks.
207 361
208=item read_size => <bytes> 362=item read_size => <bytes>
209 363
210The default read block size (the amount of bytes this module will try to read 364The initial read block size, the number of bytes this module will try to
211during each (loop iteration). Default: C<8192>. 365read during each loop iteration. Each handle object will consume at least
366this amount of memory for the read buffer as well, so when handling many
367connections requirements). See also C<max_read_size>. Default: C<2048>.
368
369=item max_read_size => <bytes>
370
371The maximum read buffer size used by the dynamic adjustment
372algorithm: Each time AnyEvent::Handle can read C<read_size> bytes in
373one go it will double C<read_size> up to the maximum given by this
374option. Default: C<131072> or C<read_size>, whichever is higher.
212 375
213=item low_water_mark => <bytes> 376=item low_water_mark => <bytes>
214 377
215Sets the amount of bytes (default: C<0>) that make up an "empty" write 378Sets the number of bytes (default: C<0>) that make up an "empty" write
216buffer: If the write reaches this size or gets even samller it is 379buffer: If the buffer reaches this size or gets even samller it is
217considered empty. 380considered empty.
218 381
382Sometimes it can be beneficial (for performance reasons) to add data to
383the write buffer before it is fully drained, but this is a rare case, as
384the operating system kernel usually buffers data as well, so the default
385is good in almost all cases.
386
219=item linger => <seconds> 387=item linger => <seconds>
220 388
221If non-zero (default: C<3600>), then the destructor of the 389If this is non-zero (default: C<3600>), the destructor of the
222AnyEvent::Handle object will check wether there is still outstanding write 390AnyEvent::Handle object will check whether there is still outstanding
223data and will install a watcher that will write out this data. No errors 391write data and will install a watcher that will write this data to the
224will be reported (this mostly matches how the operating system treats 392socket. No errors will be reported (this mostly matches how the operating
225outstanding data at socket close time). 393system treats outstanding data at socket close time).
226 394
227This will not work for partial TLS data that could not yet been 395This will not work for partial TLS data that could not be encoded
228encoded. This data will be lost. 396yet. This data will be lost. Calling the C<stoptls> method in time might
397help.
398
399=item peername => $string
400
401A string used to identify the remote site - usually the DNS hostname
402(I<not> IDN!) used to create the connection, rarely the IP address.
403
404Apart from being useful in error messages, this string is also used in TLS
405peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This
406verification will be skipped when C<peername> is not specified or is
407C<undef>.
229 408
230=item tls => "accept" | "connect" | Net::SSLeay::SSL object 409=item tls => "accept" | "connect" | Net::SSLeay::SSL object
231 410
232When this parameter is given, it enables TLS (SSL) mode, that means it 411When this parameter is given, it enables TLS (SSL) mode, that means
233will start making tls handshake and will transparently encrypt/decrypt 412AnyEvent will start a TLS handshake as soon as the connection has been
234data. 413established and will transparently encrypt/decrypt data afterwards.
414
415All TLS protocol errors will be signalled as C<EPROTO>, with an
416appropriate error message.
235 417
236TLS mode requires Net::SSLeay to be installed (it will be loaded 418TLS mode requires Net::SSLeay to be installed (it will be loaded
237automatically when you try to create a TLS handle). 419automatically when you try to create a TLS handle): this module doesn't
420have a dependency on that module, so if your module requires it, you have
421to add the dependency yourself.
238 422
239For the TLS server side, use C<accept>, and for the TLS client side of a 423Unlike TCP, TLS has a server and client side: for the TLS server side, use
240connection, use C<connect> mode. 424C<accept>, and for the TLS client side of a connection, use C<connect>
425mode.
241 426
242You can also provide your own TLS connection object, but you have 427You can also provide your own TLS connection object, but you have
243to make sure that you call either C<Net::SSLeay::set_connect_state> 428to make sure that you call either C<Net::SSLeay::set_connect_state>
244or C<Net::SSLeay::set_accept_state> on it before you pass it to 429or C<Net::SSLeay::set_accept_state> on it before you pass it to
245AnyEvent::Handle. 430AnyEvent::Handle. Also, this module will take ownership of this connection
431object.
246 432
433At some future point, AnyEvent::Handle might switch to another TLS
434implementation, then the option to use your own session object will go
435away.
436
437B<IMPORTANT:> since Net::SSLeay "objects" are really only integers,
438passing in the wrong integer will lead to certain crash. This most often
439happens when one uses a stylish C<< tls => 1 >> and is surprised about the
440segmentation fault.
441
247See the C<starttls> method if you need to start TLS negotiation later. 442Use the C<< ->starttls >> method if you need to start TLS negotiation later.
248 443
249=item tls_ctx => $ssl_ctx 444=item tls_ctx => $anyevent_tls
250 445
251Use the given Net::SSLeay::CTX object to create the new TLS connection 446Use the given C<AnyEvent::TLS> object to create the new TLS connection
252(unless a connection object was specified directly). If this parameter is 447(unless a connection object was specified directly). If this
253missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. 448parameter is missing (or C<undef>), then AnyEvent::Handle will use
449C<AnyEvent::Handle::TLS_CTX>.
450
451Instead of an object, you can also specify a hash reference with C<< key
452=> value >> pairs. Those will be passed to L<AnyEvent::TLS> to create a
453new TLS context object.
454
455=item on_starttls => $cb->($handle, $success[, $error_message])
456
457This callback will be invoked when the TLS/SSL handshake has finished. If
458C<$success> is true, then the TLS handshake succeeded, otherwise it failed
459(C<on_stoptls> will not be called in this case).
460
461The session in C<< $handle->{tls} >> can still be examined in this
462callback, even when the handshake was not successful.
463
464TLS handshake failures will not cause C<on_error> to be invoked when this
465callback is in effect, instead, the error message will be passed to C<on_starttls>.
466
467Without this callback, handshake failures lead to C<on_error> being
468called as usual.
469
470Note that you cannot just call C<starttls> again in this callback. If you
471need to do that, start an zero-second timer instead whose callback can
472then call C<< ->starttls >> again.
473
474=item on_stoptls => $cb->($handle)
475
476When a SSLv3/TLS shutdown/close notify/EOF is detected and this callback is
477set, then it will be invoked after freeing the TLS session. If it is not,
478then a TLS shutdown condition will be treated like a normal EOF condition
479on the handle.
480
481The session in C<< $handle->{tls} >> can still be examined in this
482callback.
483
484This callback will only be called on TLS shutdowns, not when the
485underlying handle signals EOF.
254 486
255=item json => JSON or JSON::XS object 487=item json => JSON or JSON::XS object
256 488
257This is the json coder object used by the C<json> read and write types. 489This is the json coder object used by the C<json> read and write types.
258 490
259If you don't supply it, then AnyEvent::Handle will create and use a 491If you don't supply it, then AnyEvent::Handle will create and use a
260suitable one, which will write and expect UTF-8 encoded JSON texts. 492suitable one (on demand), which will write and expect UTF-8 encoded JSON
493texts.
261 494
262Note that you are responsible to depend on the JSON module if you want to 495Note that you are responsible to depend on the JSON module if you want to
263use this functionality, as AnyEvent does not have a dependency itself. 496use this functionality, as AnyEvent does not have a dependency itself.
264 497
265=item filter_r => $cb
266
267=item filter_w => $cb
268
269These exist, but are undocumented at this time.
270
271=back 498=back
272 499
273=cut 500=cut
274 501
275sub new { 502sub new {
276 my $class = shift; 503 my $class = shift;
277
278 my $self = bless { @_ }, $class; 504 my $self = bless { @_ }, $class;
279 505
280 $self->{fh} or Carp::croak "mandatory argument fh is missing"; 506 if ($self->{fh}) {
507 $self->_start;
508 return unless $self->{fh}; # could be gone by now
509
510 } elsif ($self->{connect}) {
511 require AnyEvent::Socket;
512
513 $self->{peername} = $self->{connect}[0]
514 unless exists $self->{peername};
515
516 $self->{_skip_drain_rbuf} = 1;
517
518 {
519 Scalar::Util::weaken (my $self = $self);
520
521 $self->{_connect} =
522 AnyEvent::Socket::tcp_connect (
523 $self->{connect}[0],
524 $self->{connect}[1],
525 sub {
526 my ($fh, $host, $port, $retry) = @_;
527
528 delete $self->{_connect}; # no longer needed
529
530 if ($fh) {
531 $self->{fh} = $fh;
532
533 delete $self->{_skip_drain_rbuf};
534 $self->_start;
535
536 $self->{on_connect}
537 and $self->{on_connect}($self, $host, $port, sub {
538 delete @$self{qw(fh _tw _rtw _wtw _ww _rw _eof _queue rbuf _wbuf tls _tls_rbuf _tls_wbuf)};
539 $self->{_skip_drain_rbuf} = 1;
540 &$retry;
541 });
542
543 } else {
544 if ($self->{on_connect_error}) {
545 $self->{on_connect_error}($self, "$!");
546 $self->destroy if $self;
547 } else {
548 $self->_error ($!, 1);
549 }
550 }
551 },
552 sub {
553 local $self->{fh} = $_[0];
554
555 $self->{on_prepare}
556 ? $self->{on_prepare}->($self)
557 : ()
558 }
559 );
560 }
561
562 } else {
563 Carp::croak "AnyEvent::Handle: either an existing fh or the connect parameter must be specified";
564 }
565
566 $self
567}
568
569sub _start {
570 my ($self) = @_;
571
572 # too many clueless people try to use udp and similar sockets
573 # with AnyEvent::Handle, do them a favour.
574 my $type = getsockopt $self->{fh}, Socket::SOL_SOCKET (), Socket::SO_TYPE ();
575 Carp::croak "AnyEvent::Handle: only stream sockets supported, anything else will NOT work!"
576 if Socket::SOCK_STREAM () != (unpack "I", $type) && defined $type;
281 577
282 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 578 AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
283 579
284 if ($self->{tls}) { 580 $self->{_activity} =
285 require Net::SSLeay; 581 $self->{_ractivity} =
582 $self->{_wactivity} = AE::now;
583
584 $self->{read_size} ||= 2048;
585 $self->{max_read_size} = $self->{read_size}
586 if $self->{read_size} > ($self->{max_read_size} || MAX_READ_SIZE);
587
588 $self->timeout (delete $self->{timeout} ) if $self->{timeout};
589 $self->rtimeout (delete $self->{rtimeout} ) if $self->{rtimeout};
590 $self->wtimeout (delete $self->{wtimeout} ) if $self->{wtimeout};
591
592 $self->no_delay (delete $self->{no_delay} ) if exists $self->{no_delay} && $self->{no_delay};
593 $self->keepalive (delete $self->{keepalive}) if exists $self->{keepalive} && $self->{keepalive};
594
595 $self->oobinline (exists $self->{oobinline} ? delete $self->{oobinline} : 1);
596
286 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx}); 597 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
287 } 598 if $self->{tls};
288 599
289 $self->{_activity} = AnyEvent->now;
290 $self->_timeout;
291
292 $self->on_drain (delete $self->{on_drain}) if exists $self->{on_drain}; 600 $self->on_drain (delete $self->{on_drain} ) if $self->{on_drain};
293 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay};
294 601
295 $self->start_read 602 $self->start_read
296 if $self->{on_read}; 603 if $self->{on_read} || @{ $self->{_queue} };
297 604
298 $self 605 $self->_drain_wbuf;
299}
300
301sub _shutdown {
302 my ($self) = @_;
303
304 delete $self->{_tw};
305 delete $self->{_rw};
306 delete $self->{_ww};
307 delete $self->{fh};
308
309 $self->stoptls;
310
311 delete $self->{on_read};
312 delete $self->{_queue};
313} 606}
314 607
315sub _error { 608sub _error {
316 my ($self, $errno, $fatal) = @_; 609 my ($self, $errno, $fatal, $message) = @_;
317
318 $self->_shutdown
319 if $fatal;
320 610
321 $! = $errno; 611 $! = $errno;
612 $message ||= "$!";
322 613
323 if ($self->{on_error}) { 614 if ($self->{on_error}) {
324 $self->{on_error}($self, $fatal); 615 $self->{on_error}($self, $fatal, $message);
325 } else { 616 $self->destroy if $fatal;
617 } elsif ($self->{fh} || $self->{connect}) {
618 $self->destroy;
326 Carp::croak "AnyEvent::Handle uncaught error: $!"; 619 Carp::croak "AnyEvent::Handle uncaught error: $message";
327 } 620 }
328} 621}
329 622
330=item $fh = $handle->fh 623=item $fh = $handle->fh
331 624
332This method returns the file handle of the L<AnyEvent::Handle> object. 625This method returns the file handle used to create the L<AnyEvent::Handle> object.
333 626
334=cut 627=cut
335 628
336sub fh { $_[0]{fh} } 629sub fh { $_[0]{fh} }
337 630
355 $_[0]{on_eof} = $_[1]; 648 $_[0]{on_eof} = $_[1];
356} 649}
357 650
358=item $handle->on_timeout ($cb) 651=item $handle->on_timeout ($cb)
359 652
360Replace the current C<on_timeout> callback, or disables the callback 653=item $handle->on_rtimeout ($cb)
361(but not the timeout) if C<$cb> = C<undef>. See C<timeout> constructor
362argument.
363 654
364=cut 655=item $handle->on_wtimeout ($cb)
365 656
366sub on_timeout { 657Replace the current C<on_timeout>, C<on_rtimeout> or C<on_wtimeout>
367 $_[0]{on_timeout} = $_[1]; 658callback, or disables the callback (but not the timeout) if C<$cb> =
368} 659C<undef>. See the C<timeout> constructor argument and method.
660
661=cut
662
663# see below
369 664
370=item $handle->autocork ($boolean) 665=item $handle->autocork ($boolean)
371 666
372Enables or disables the current autocork behaviour (see C<autocork> 667Enables or disables the current autocork behaviour (see C<autocork>
373constructor argument). 668constructor argument). Changes will only take effect on the next write.
374 669
375=cut 670=cut
671
672sub autocork {
673 $_[0]{autocork} = $_[1];
674}
376 675
377=item $handle->no_delay ($boolean) 676=item $handle->no_delay ($boolean)
378 677
379Enables or disables the C<no_delay> setting (see constructor argument of 678Enables or disables the C<no_delay> setting (see constructor argument of
380the same name for details). 679the same name for details).
382=cut 681=cut
383 682
384sub no_delay { 683sub no_delay {
385 $_[0]{no_delay} = $_[1]; 684 $_[0]{no_delay} = $_[1];
386 685
686 setsockopt $_[0]{fh}, Socket::IPPROTO_TCP (), Socket::TCP_NODELAY (), int $_[1]
687 if $_[0]{fh};
688}
689
690=item $handle->keepalive ($boolean)
691
692Enables or disables the C<keepalive> setting (see constructor argument of
693the same name for details).
694
695=cut
696
697sub keepalive {
698 $_[0]{keepalive} = $_[1];
699
387 eval { 700 eval {
388 local $SIG{__DIE__}; 701 local $SIG{__DIE__};
389 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1]; 702 setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_KEEPALIVE (), int $_[1]
703 if $_[0]{fh};
390 }; 704 };
391} 705}
392 706
707=item $handle->oobinline ($boolean)
708
709Enables or disables the C<oobinline> setting (see constructor argument of
710the same name for details).
711
712=cut
713
714sub oobinline {
715 $_[0]{oobinline} = $_[1];
716
717 eval {
718 local $SIG{__DIE__};
719 setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_OOBINLINE (), int $_[1]
720 if $_[0]{fh};
721 };
722}
723
724=item $handle->keepalive ($boolean)
725
726Enables or disables the C<keepalive> setting (see constructor argument of
727the same name for details).
728
729=cut
730
731sub keepalive {
732 $_[0]{keepalive} = $_[1];
733
734 eval {
735 local $SIG{__DIE__};
736 setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_KEEPALIVE (), int $_[1]
737 if $_[0]{fh};
738 };
739}
740
741=item $handle->on_starttls ($cb)
742
743Replace the current C<on_starttls> callback (see the C<on_starttls> constructor argument).
744
745=cut
746
747sub on_starttls {
748 $_[0]{on_starttls} = $_[1];
749}
750
751=item $handle->on_stoptls ($cb)
752
753Replace the current C<on_stoptls> callback (see the C<on_stoptls> constructor argument).
754
755=cut
756
757sub on_stoptls {
758 $_[0]{on_stoptls} = $_[1];
759}
760
761=item $handle->rbuf_max ($max_octets)
762
763Configures the C<rbuf_max> setting (C<undef> disables it).
764
765=item $handle->wbuf_max ($max_octets)
766
767Configures the C<wbuf_max> setting (C<undef> disables it).
768
769=cut
770
771sub rbuf_max {
772 $_[0]{rbuf_max} = $_[1];
773}
774
775sub wbuf_max {
776 $_[0]{wbuf_max} = $_[1];
777}
778
393############################################################################# 779#############################################################################
394 780
395=item $handle->timeout ($seconds) 781=item $handle->timeout ($seconds)
396 782
783=item $handle->rtimeout ($seconds)
784
785=item $handle->wtimeout ($seconds)
786
397Configures (or disables) the inactivity timeout. 787Configures (or disables) the inactivity timeout.
398 788
399=cut 789The timeout will be checked instantly, so this method might destroy the
790handle before it returns.
400 791
401sub timeout { 792=item $handle->timeout_reset
793
794=item $handle->rtimeout_reset
795
796=item $handle->wtimeout_reset
797
798Reset the activity timeout, as if data was received or sent.
799
800These methods are cheap to call.
801
802=cut
803
804for my $dir ("", "r", "w") {
805 my $timeout = "${dir}timeout";
806 my $tw = "_${dir}tw";
807 my $on_timeout = "on_${dir}timeout";
808 my $activity = "_${dir}activity";
809 my $cb;
810
811 *$on_timeout = sub {
812 $_[0]{$on_timeout} = $_[1];
813 };
814
815 *$timeout = sub {
402 my ($self, $timeout) = @_; 816 my ($self, $new_value) = @_;
403 817
818 $new_value >= 0
819 or Carp::croak "AnyEvent::Handle->$timeout called with negative timeout ($new_value), caught";
820
404 $self->{timeout} = $timeout; 821 $self->{$timeout} = $new_value;
405 $self->_timeout; 822 delete $self->{$tw}; &$cb;
406} 823 };
407 824
825 *{"${dir}timeout_reset"} = sub {
826 $_[0]{$activity} = AE::now;
827 };
828
829 # main workhorse:
408# reset the timeout watcher, as neccessary 830 # reset the timeout watcher, as neccessary
409# also check for time-outs 831 # also check for time-outs
410sub _timeout { 832 $cb = sub {
411 my ($self) = @_; 833 my ($self) = @_;
412 834
413 if ($self->{timeout}) { 835 if ($self->{$timeout} && $self->{fh}) {
414 my $NOW = AnyEvent->now; 836 my $NOW = AE::now;
415 837
416 # when would the timeout trigger? 838 # when would the timeout trigger?
417 my $after = $self->{_activity} + $self->{timeout} - $NOW; 839 my $after = $self->{$activity} + $self->{$timeout} - $NOW;
418 840
419 # now or in the past already? 841 # now or in the past already?
420 if ($after <= 0) { 842 if ($after <= 0) {
421 $self->{_activity} = $NOW; 843 $self->{$activity} = $NOW;
422 844
423 if ($self->{on_timeout}) { 845 if ($self->{$on_timeout}) {
424 $self->{on_timeout}($self); 846 $self->{$on_timeout}($self);
425 } else { 847 } else {
426 $self->_error (&Errno::ETIMEDOUT); 848 $self->_error (Errno::ETIMEDOUT);
849 }
850
851 # callback could have changed timeout value, optimise
852 return unless $self->{$timeout};
853
854 # calculate new after
855 $after = $self->{$timeout};
427 } 856 }
428 857
429 # callback could have changed timeout value, optimise 858 Scalar::Util::weaken $self;
430 return unless $self->{timeout}; 859 return unless $self; # ->error could have destroyed $self
431 860
432 # calculate new after 861 $self->{$tw} ||= AE::timer $after, 0, sub {
433 $after = $self->{timeout}; 862 delete $self->{$tw};
863 $cb->($self);
864 };
865 } else {
866 delete $self->{$tw};
434 } 867 }
435
436 Scalar::Util::weaken $self;
437 return unless $self; # ->error could have destroyed $self
438
439 $self->{_tw} ||= AnyEvent->timer (after => $after, cb => sub {
440 delete $self->{_tw};
441 $self->_timeout;
442 });
443 } else {
444 delete $self->{_tw};
445 } 868 }
446} 869}
447 870
448############################################################################# 871#############################################################################
449 872
465=item $handle->on_drain ($cb) 888=item $handle->on_drain ($cb)
466 889
467Sets the C<on_drain> callback or clears it (see the description of 890Sets the C<on_drain> callback or clears it (see the description of
468C<on_drain> in the constructor). 891C<on_drain> in the constructor).
469 892
893This method may invoke callbacks (and therefore the handle might be
894destroyed after it returns).
895
470=cut 896=cut
471 897
472sub on_drain { 898sub on_drain {
473 my ($self, $cb) = @_; 899 my ($self, $cb) = @_;
474 900
475 $self->{on_drain} = $cb; 901 $self->{on_drain} = $cb;
476 902
477 $cb->($self) 903 $cb->($self)
478 if $cb && $self->{low_water_mark} >= length $self->{wbuf}; 904 if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
479} 905}
480 906
481=item $handle->push_write ($data) 907=item $handle->push_write ($data)
482 908
483Queues the given scalar to be written. You can push as much data as you 909Queues the given scalar to be written. You can push as much data as
484want (only limited by the available memory), as C<AnyEvent::Handle> 910you want (only limited by the available memory and C<wbuf_max>), as
485buffers it independently of the kernel. 911C<AnyEvent::Handle> buffers it independently of the kernel.
912
913This method may invoke callbacks (and therefore the handle might be
914destroyed after it returns).
486 915
487=cut 916=cut
488 917
489sub _drain_wbuf { 918sub _drain_wbuf {
490 my ($self) = @_; 919 my ($self) = @_;
494 Scalar::Util::weaken $self; 923 Scalar::Util::weaken $self;
495 924
496 my $cb = sub { 925 my $cb = sub {
497 my $len = syswrite $self->{fh}, $self->{wbuf}; 926 my $len = syswrite $self->{fh}, $self->{wbuf};
498 927
499 if ($len >= 0) { 928 if (defined $len) {
500 substr $self->{wbuf}, 0, $len, ""; 929 substr $self->{wbuf}, 0, $len, "";
501 930
502 $self->{_activity} = AnyEvent->now; 931 $self->{_activity} = $self->{_wactivity} = AE::now;
503 932
504 $self->{on_drain}($self) 933 $self->{on_drain}($self)
505 if $self->{low_water_mark} >= length $self->{wbuf} 934 if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
506 && $self->{on_drain}; 935 && $self->{on_drain};
507 936
508 delete $self->{_ww} unless length $self->{wbuf}; 937 delete $self->{_ww} unless length $self->{wbuf};
509 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { 938 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
510 $self->_error ($!, 1); 939 $self->_error ($!, 1);
513 942
514 # try to write data immediately 943 # try to write data immediately
515 $cb->() unless $self->{autocork}; 944 $cb->() unless $self->{autocork};
516 945
517 # if still data left in wbuf, we need to poll 946 # if still data left in wbuf, we need to poll
518 $self->{_ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb) 947 $self->{_ww} = AE::io $self->{fh}, 1, $cb
519 if length $self->{wbuf}; 948 if length $self->{wbuf};
949
950 if (
951 defined $self->{wbuf_max}
952 && $self->{wbuf_max} < length $self->{wbuf}
953 ) {
954 $self->_error (Errno::ENOSPC, 1), return;
955 }
520 }; 956 };
521} 957}
522 958
523our %WH; 959our %WH;
524 960
961# deprecated
525sub register_write_type($$) { 962sub register_write_type($$) {
526 $WH{$_[0]} = $_[1]; 963 $WH{$_[0]} = $_[1];
527} 964}
528 965
529sub push_write { 966sub push_write {
530 my $self = shift; 967 my $self = shift;
531 968
532 if (@_ > 1) { 969 if (@_ > 1) {
533 my $type = shift; 970 my $type = shift;
534 971
972 @_ = ($WH{$type} ||= _load_func "$type\::anyevent_write_type"
535 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write") 973 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::push_write")
536 ->($self, @_); 974 ->($self, @_);
537 } 975 }
538 976
977 # we downgrade here to avoid hard-to-track-down bugs,
978 # and diagnose the problem earlier and better.
979
539 if ($self->{filter_w}) { 980 if ($self->{tls}) {
540 $self->{filter_w}($self, \$_[0]); 981 utf8::downgrade $self->{_tls_wbuf} .= $_[0];
982 &_dotls ($self) if $self->{fh};
541 } else { 983 } else {
542 $self->{wbuf} .= $_[0]; 984 utf8::downgrade $self->{wbuf} .= $_[0];
543 $self->_drain_wbuf; 985 $self->_drain_wbuf if $self->{fh};
544 } 986 }
545} 987}
546 988
547=item $handle->push_write (type => @args) 989=item $handle->push_write (type => @args)
548 990
549Instead of formatting your data yourself, you can also let this module do 991Instead of formatting your data yourself, you can also let this module
550the job by specifying a type and type-specific arguments. 992do the job by specifying a type and type-specific arguments. You
993can also specify the (fully qualified) name of a package, in which
994case AnyEvent tries to load the package and then expects to find the
995C<anyevent_write_type> function inside (see "custom write types", below).
551 996
552Predefined types are (if you have ideas for additional types, feel free to 997Predefined types are (if you have ideas for additional types, feel free to
553drop by and tell us): 998drop by and tell us):
554 999
555=over 4 1000=over 4
562=cut 1007=cut
563 1008
564register_write_type netstring => sub { 1009register_write_type netstring => sub {
565 my ($self, $string) = @_; 1010 my ($self, $string) = @_;
566 1011
567 sprintf "%d:%s,", (length $string), $string 1012 (length $string) . ":$string,"
568}; 1013};
569 1014
570=item packstring => $format, $data 1015=item packstring => $format, $data
571 1016
572An octet string prefixed with an encoded length. The encoding C<$format> 1017An octet string prefixed with an encoded length. The encoding C<$format>
612Other languages could read single lines terminated by a newline and pass 1057Other languages could read single lines terminated by a newline and pass
613this line into their JSON decoder of choice. 1058this line into their JSON decoder of choice.
614 1059
615=cut 1060=cut
616 1061
1062sub json_coder() {
1063 eval { require JSON::XS; JSON::XS->new->utf8 }
1064 || do { require JSON; JSON->new->utf8 }
1065}
1066
617register_write_type json => sub { 1067register_write_type json => sub {
618 my ($self, $ref) = @_; 1068 my ($self, $ref) = @_;
619 1069
620 require JSON; 1070 my $json = $self->{json} ||= json_coder;
621 1071
622 $self->{json} ? $self->{json}->encode ($ref) 1072 $json->encode ($ref)
623 : JSON::encode_json ($ref)
624}; 1073};
625 1074
626=item storable => $reference 1075=item storable => $reference
627 1076
628Freezes the given reference using L<Storable> and writes it to the 1077Freezes the given reference using L<Storable> and writes it to the
638 pack "w/a*", Storable::nfreeze ($ref) 1087 pack "w/a*", Storable::nfreeze ($ref)
639}; 1088};
640 1089
641=back 1090=back
642 1091
643=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args) 1092=item $handle->push_shutdown
644 1093
645This function (not method) lets you add your own types to C<push_write>. 1094Sometimes you know you want to close the socket after writing your data
1095before it was actually written. One way to do that is to replace your
1096C<on_drain> handler by a callback that shuts down the socket (and set
1097C<low_water_mark> to C<0>). This method is a shorthand for just that, and
1098replaces the C<on_drain> callback with:
1099
1100 sub { shutdown $_[0]{fh}, 1 }
1101
1102This simply shuts down the write side and signals an EOF condition to the
1103the peer.
1104
1105You can rely on the normal read queue and C<on_eof> handling
1106afterwards. This is the cleanest way to close a connection.
1107
1108This method may invoke callbacks (and therefore the handle might be
1109destroyed after it returns).
1110
1111=cut
1112
1113sub push_shutdown {
1114 my ($self) = @_;
1115
1116 delete $self->{low_water_mark};
1117 $self->on_drain (sub { shutdown $_[0]{fh}, 1 });
1118}
1119
1120=item custom write types - Package::anyevent_write_type $handle, @args
1121
1122Instead of one of the predefined types, you can also specify the name of
1123a package. AnyEvent will try to load the package and then expects to find
1124a function named C<anyevent_write_type> inside. If it isn't found, it
1125progressively tries to load the parent package until it either finds the
1126function (good) or runs out of packages (bad).
1127
646Whenever the given C<type> is used, C<push_write> will invoke the code 1128Whenever the given C<type> is used, C<push_write> will the function with
647reference with the handle object and the remaining arguments. 1129the handle object and the remaining arguments.
648 1130
649The code reference is supposed to return a single octet string that will 1131The function is supposed to return a single octet string that will be
650be appended to the write buffer. 1132appended to the write buffer, so you cna mentally treat this function as a
1133"arguments to on-the-wire-format" converter.
651 1134
652Note that this is a function, and all types registered this way will be 1135Example: implement a custom write type C<join> that joins the remaining
653global, so try to use unique names. 1136arguments using the first one.
1137
1138 $handle->push_write (My::Type => " ", 1,2,3);
1139
1140 # uses the following package, which can be defined in the "My::Type" or in
1141 # the "My" modules to be auto-loaded, or just about anywhere when the
1142 # My::Type::anyevent_write_type is defined before invoking it.
1143
1144 package My::Type;
1145
1146 sub anyevent_write_type {
1147 my ($handle, $delim, @args) = @_;
1148
1149 join $delim, @args
1150 }
654 1151
655=cut 1152=cut
656 1153
657############################################################################# 1154#############################################################################
658 1155
667ways, the "simple" way, using only C<on_read> and the "complex" way, using 1164ways, the "simple" way, using only C<on_read> and the "complex" way, using
668a queue. 1165a queue.
669 1166
670In the simple case, you just install an C<on_read> callback and whenever 1167In the simple case, you just install an C<on_read> callback and whenever
671new data arrives, it will be called. You can then remove some data (if 1168new data arrives, it will be called. You can then remove some data (if
672enough is there) from the read buffer (C<< $handle->rbuf >>). Or you cna 1169enough is there) from the read buffer (C<< $handle->rbuf >>). Or you can
673leave the data there if you want to accumulate more (e.g. when only a 1170leave the data there if you want to accumulate more (e.g. when only a
674partial message has been received so far). 1171partial message has been received so far), or change the read queue with
1172e.g. C<push_read>.
675 1173
676In the more complex case, you want to queue multiple callbacks. In this 1174In the more complex case, you want to queue multiple callbacks. In this
677case, AnyEvent::Handle will call the first queued callback each time new 1175case, AnyEvent::Handle will call the first queued callback each time new
678data arrives (also the first time it is queued) and removes it when it has 1176data arrives (also the first time it is queued) and remove it when it has
679done its job (see C<push_read>, below). 1177done its job (see C<push_read>, below).
680 1178
681This way you can, for example, push three line-reads, followed by reading 1179This way you can, for example, push three line-reads, followed by reading
682a chunk of data, and AnyEvent::Handle will execute them in order. 1180a chunk of data, and AnyEvent::Handle will execute them in order.
683 1181
740=cut 1238=cut
741 1239
742sub _drain_rbuf { 1240sub _drain_rbuf {
743 my ($self) = @_; 1241 my ($self) = @_;
744 1242
1243 # avoid recursion
1244 return if $self->{_skip_drain_rbuf};
745 local $self->{_in_drain} = 1; 1245 local $self->{_skip_drain_rbuf} = 1;
746
747 if (
748 defined $self->{rbuf_max}
749 && $self->{rbuf_max} < length $self->{rbuf}
750 ) {
751 $self->_error (&Errno::ENOSPC, 1), return;
752 }
753 1246
754 while () { 1247 while () {
1248 # we need to use a separate tls read buffer, as we must not receive data while
1249 # we are draining the buffer, and this can only happen with TLS.
1250 $self->{rbuf} .= delete $self->{_tls_rbuf}
1251 if exists $self->{_tls_rbuf};
1252
755 my $len = length $self->{rbuf}; 1253 my $len = length $self->{rbuf};
756 1254
757 if (my $cb = shift @{ $self->{_queue} }) { 1255 if (my $cb = shift @{ $self->{_queue} }) {
758 unless ($cb->($self)) { 1256 unless ($cb->($self)) {
759 if ($self->{_eof}) { 1257 # no progress can be made
760 # no progress can be made (not enough data and no data forthcoming) 1258 # (not enough data and no data forthcoming)
761 $self->_error (&Errno::EPIPE, 1), return; 1259 $self->_error (Errno::EPIPE, 1), return
762 } 1260 if $self->{_eof};
763 1261
764 unshift @{ $self->{_queue} }, $cb; 1262 unshift @{ $self->{_queue} }, $cb;
765 last; 1263 last;
766 } 1264 }
767 } elsif ($self->{on_read}) { 1265 } elsif ($self->{on_read}) {
774 && !@{ $self->{_queue} } # and the queue is still empty 1272 && !@{ $self->{_queue} } # and the queue is still empty
775 && $self->{on_read} # but we still have on_read 1273 && $self->{on_read} # but we still have on_read
776 ) { 1274 ) {
777 # no further data will arrive 1275 # no further data will arrive
778 # so no progress can be made 1276 # so no progress can be made
779 $self->_error (&Errno::EPIPE, 1), return 1277 $self->_error (Errno::EPIPE, 1), return
780 if $self->{_eof}; 1278 if $self->{_eof};
781 1279
782 last; # more data might arrive 1280 last; # more data might arrive
783 } 1281 }
784 } else { 1282 } else {
785 # read side becomes idle 1283 # read side becomes idle
786 delete $self->{_rw}; 1284 delete $self->{_rw} unless $self->{tls};
787 last; 1285 last;
788 } 1286 }
789 } 1287 }
790 1288
791 if ($self->{_eof}) { 1289 if ($self->{_eof}) {
792 if ($self->{on_eof}) { 1290 $self->{on_eof}
793 $self->{on_eof}($self) 1291 ? $self->{on_eof}($self)
794 } else { 1292 : $self->_error (0, 1, "Unexpected end-of-file");
795 $self->_error (0, 1); 1293
796 } 1294 return;
1295 }
1296
1297 if (
1298 defined $self->{rbuf_max}
1299 && $self->{rbuf_max} < length $self->{rbuf}
1300 ) {
1301 $self->_error (Errno::ENOSPC, 1), return;
797 } 1302 }
798 1303
799 # may need to restart read watcher 1304 # may need to restart read watcher
800 unless ($self->{_rw}) { 1305 unless ($self->{_rw}) {
801 $self->start_read 1306 $self->start_read
807 1312
808This replaces the currently set C<on_read> callback, or clears it (when 1313This replaces the currently set C<on_read> callback, or clears it (when
809the new callback is C<undef>). See the description of C<on_read> in the 1314the new callback is C<undef>). See the description of C<on_read> in the
810constructor. 1315constructor.
811 1316
1317This method may invoke callbacks (and therefore the handle might be
1318destroyed after it returns).
1319
812=cut 1320=cut
813 1321
814sub on_read { 1322sub on_read {
815 my ($self, $cb) = @_; 1323 my ($self, $cb) = @_;
816 1324
817 $self->{on_read} = $cb; 1325 $self->{on_read} = $cb;
818 $self->_drain_rbuf if $cb && !$self->{_in_drain}; 1326 $self->_drain_rbuf if $cb;
819} 1327}
820 1328
821=item $handle->rbuf 1329=item $handle->rbuf
822 1330
823Returns the read buffer (as a modifiable lvalue). 1331Returns the read buffer (as a modifiable lvalue). You can also access the
1332read buffer directly as the C<< ->{rbuf} >> member, if you want (this is
1333much faster, and no less clean).
824 1334
825You can access the read buffer directly as the C<< ->{rbuf} >> member, if 1335The only operation allowed on the read buffer (apart from looking at it)
826you want. 1336is removing data from its beginning. Otherwise modifying or appending to
1337it is not allowed and will lead to hard-to-track-down bugs.
827 1338
828NOTE: The read buffer should only be used or modified if the C<on_read>, 1339NOTE: The read buffer should only be used or modified in the C<on_read>
829C<push_read> or C<unshift_read> methods are used. The other read methods 1340callback or when C<push_read> or C<unshift_read> are used with a single
830automatically manage the read buffer. 1341callback (i.e. untyped). Typed C<push_read> and C<unshift_read> methods
1342will manage the read buffer on their own.
831 1343
832=cut 1344=cut
833 1345
834sub rbuf : lvalue { 1346sub rbuf : lvalue {
835 $_[0]{rbuf} 1347 $_[0]{rbuf}
852 1364
853If enough data was available, then the callback must remove all data it is 1365If enough data was available, then the callback must remove all data it is
854interested in (which can be none at all) and return a true value. After returning 1366interested in (which can be none at all) and return a true value. After returning
855true, it will be removed from the queue. 1367true, it will be removed from the queue.
856 1368
1369These methods may invoke callbacks (and therefore the handle might be
1370destroyed after it returns).
1371
857=cut 1372=cut
858 1373
859our %RH; 1374our %RH;
860 1375
861sub register_read_type($$) { 1376sub register_read_type($$) {
867 my $cb = pop; 1382 my $cb = pop;
868 1383
869 if (@_) { 1384 if (@_) {
870 my $type = shift; 1385 my $type = shift;
871 1386
1387 $cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
872 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_read") 1388 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::push_read")
873 ->($self, $cb, @_); 1389 ->($self, $cb, @_);
874 } 1390 }
875 1391
876 push @{ $self->{_queue} }, $cb; 1392 push @{ $self->{_queue} }, $cb;
877 $self->_drain_rbuf unless $self->{_in_drain}; 1393 $self->_drain_rbuf;
878} 1394}
879 1395
880sub unshift_read { 1396sub unshift_read {
881 my $self = shift; 1397 my $self = shift;
882 my $cb = pop; 1398 my $cb = pop;
883 1399
884 if (@_) { 1400 if (@_) {
885 my $type = shift; 1401 my $type = shift;
886 1402
1403 $cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
887 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::unshift_read") 1404 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::unshift_read")
888 ->($self, $cb, @_); 1405 ->($self, $cb, @_);
889 } 1406 }
890 1407
891
892 unshift @{ $self->{_queue} }, $cb; 1408 unshift @{ $self->{_queue} }, $cb;
893 $self->_drain_rbuf unless $self->{_in_drain}; 1409 $self->_drain_rbuf;
894} 1410}
895 1411
896=item $handle->push_read (type => @args, $cb) 1412=item $handle->push_read (type => @args, $cb)
897 1413
898=item $handle->unshift_read (type => @args, $cb) 1414=item $handle->unshift_read (type => @args, $cb)
899 1415
900Instead of providing a callback that parses the data itself you can chose 1416Instead of providing a callback that parses the data itself you can chose
901between a number of predefined parsing formats, for chunks of data, lines 1417between a number of predefined parsing formats, for chunks of data, lines
902etc. 1418etc. You can also specify the (fully qualified) name of a package, in
1419which case AnyEvent tries to load the package and then expects to find the
1420C<anyevent_read_type> function inside (see "custom read types", below).
903 1421
904Predefined types are (if you have ideas for additional types, feel free to 1422Predefined types are (if you have ideas for additional types, feel free to
905drop by and tell us): 1423drop by and tell us):
906 1424
907=over 4 1425=over 4
999the receive buffer when neither C<$accept> nor C<$reject> match, 1517the receive buffer when neither C<$accept> nor C<$reject> match,
1000and everything preceding and including the match will be accepted 1518and everything preceding and including the match will be accepted
1001unconditionally. This is useful to skip large amounts of data that you 1519unconditionally. This is useful to skip large amounts of data that you
1002know cannot be matched, so that the C<$accept> or C<$reject> regex do not 1520know cannot be matched, so that the C<$accept> or C<$reject> regex do not
1003have to start matching from the beginning. This is purely an optimisation 1521have to start matching from the beginning. This is purely an optimisation
1004and is usually worth only when you expect more than a few kilobytes. 1522and is usually worth it only when you expect more than a few kilobytes.
1005 1523
1006Example: expect a http header, which ends at C<\015\012\015\012>. Since we 1524Example: expect a http header, which ends at C<\015\012\015\012>. Since we
1007expect the header to be very large (it isn't in practise, but...), we use 1525expect the header to be very large (it isn't in practice, but...), we use
1008a skip regex to skip initial portions. The skip regex is tricky in that 1526a skip regex to skip initial portions. The skip regex is tricky in that
1009it only accepts something not ending in either \015 or \012, as these are 1527it only accepts something not ending in either \015 or \012, as these are
1010required for the accept regex. 1528required for the accept regex.
1011 1529
1012 $handle->push_read (regex => 1530 $handle->push_read (regex =>
1031 return 1; 1549 return 1;
1032 } 1550 }
1033 1551
1034 # reject 1552 # reject
1035 if ($reject && $$rbuf =~ $reject) { 1553 if ($reject && $$rbuf =~ $reject) {
1036 $self->_error (&Errno::EBADMSG); 1554 $self->_error (Errno::EBADMSG);
1037 } 1555 }
1038 1556
1039 # skip 1557 # skip
1040 if ($skip && $$rbuf =~ $skip) { 1558 if ($skip && $$rbuf =~ $skip) {
1041 $data .= substr $$rbuf, 0, $+[0], ""; 1559 $data .= substr $$rbuf, 0, $+[0], "";
1057 my ($self, $cb) = @_; 1575 my ($self, $cb) = @_;
1058 1576
1059 sub { 1577 sub {
1060 unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) { 1578 unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) {
1061 if ($_[0]{rbuf} =~ /[^0-9]/) { 1579 if ($_[0]{rbuf} =~ /[^0-9]/) {
1062 $self->_error (&Errno::EBADMSG); 1580 $self->_error (Errno::EBADMSG);
1063 } 1581 }
1064 return; 1582 return;
1065 } 1583 }
1066 1584
1067 my $len = $1; 1585 my $len = $1;
1070 my $string = $_[1]; 1588 my $string = $_[1];
1071 $_[0]->unshift_read (chunk => 1, sub { 1589 $_[0]->unshift_read (chunk => 1, sub {
1072 if ($_[1] eq ",") { 1590 if ($_[1] eq ",") {
1073 $cb->($_[0], $string); 1591 $cb->($_[0], $string);
1074 } else { 1592 } else {
1075 $self->_error (&Errno::EBADMSG); 1593 $self->_error (Errno::EBADMSG);
1076 } 1594 }
1077 }); 1595 });
1078 }); 1596 });
1079 1597
1080 1 1598 1
1086An octet string prefixed with an encoded length. The encoding C<$format> 1604An octet string prefixed with an encoded length. The encoding C<$format>
1087uses the same format as a Perl C<pack> format, but must specify a single 1605uses the same format as a Perl C<pack> format, but must specify a single
1088integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an 1606integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an
1089optional C<!>, C<< < >> or C<< > >> modifier). 1607optional C<!>, C<< < >> or C<< > >> modifier).
1090 1608
1091DNS over TCP uses a prefix of C<n>, EPP uses a prefix of C<N>. 1609For example, DNS over TCP uses a prefix of C<n> (2 octet network order),
1610EPP uses a prefix of C<N> (4 octtes).
1092 1611
1093Example: read a block of data prefixed by its length in BER-encoded 1612Example: read a block of data prefixed by its length in BER-encoded
1094format (very efficient). 1613format (very efficient).
1095 1614
1096 $handle->push_read (packstring => "w", sub { 1615 $handle->push_read (packstring => "w", sub {
1126 } 1645 }
1127}; 1646};
1128 1647
1129=item json => $cb->($handle, $hash_or_arrayref) 1648=item json => $cb->($handle, $hash_or_arrayref)
1130 1649
1131Reads a JSON object or array, decodes it and passes it to the callback. 1650Reads a JSON object or array, decodes it and passes it to the
1651callback. When a parse error occurs, an C<EBADMSG> error will be raised.
1132 1652
1133If a C<json> object was passed to the constructor, then that will be used 1653If a C<json> object was passed to the constructor, then that will be used
1134for the final decode, otherwise it will create a JSON coder expecting UTF-8. 1654for the final decode, otherwise it will create a JSON coder expecting UTF-8.
1135 1655
1136This read type uses the incremental parser available with JSON version 1656This read type uses the incremental parser available with JSON version
1145=cut 1665=cut
1146 1666
1147register_read_type json => sub { 1667register_read_type json => sub {
1148 my ($self, $cb) = @_; 1668 my ($self, $cb) = @_;
1149 1669
1150 require JSON; 1670 my $json = $self->{json} ||= json_coder;
1151 1671
1152 my $data; 1672 my $data;
1153 my $rbuf = \$self->{rbuf}; 1673 my $rbuf = \$self->{rbuf};
1154 1674
1155 my $json = $self->{json} ||= JSON->new->utf8;
1156
1157 sub { 1675 sub {
1158 my $ref = $json->incr_parse ($self->{rbuf}); 1676 my $ref = eval { $json->incr_parse ($self->{rbuf}) };
1159 1677
1160 if ($ref) { 1678 if ($ref) {
1161 $self->{rbuf} = $json->incr_text; 1679 $self->{rbuf} = $json->incr_text;
1162 $json->incr_text = ""; 1680 $json->incr_text = "";
1163 $cb->($self, $ref); 1681 $cb->($self, $ref);
1164 1682
1165 1 1683 1
1684 } elsif ($@) {
1685 # error case
1686 $json->incr_skip;
1687
1688 $self->{rbuf} = $json->incr_text;
1689 $json->incr_text = "";
1690
1691 $self->_error (Errno::EBADMSG);
1692
1693 ()
1166 } else { 1694 } else {
1167 $self->{rbuf} = ""; 1695 $self->{rbuf} = "";
1696
1168 () 1697 ()
1169 } 1698 }
1170 } 1699 }
1171}; 1700};
1172 1701
1204 # read remaining chunk 1733 # read remaining chunk
1205 $_[0]->unshift_read (chunk => $len, sub { 1734 $_[0]->unshift_read (chunk => $len, sub {
1206 if (my $ref = eval { Storable::thaw ($_[1]) }) { 1735 if (my $ref = eval { Storable::thaw ($_[1]) }) {
1207 $cb->($_[0], $ref); 1736 $cb->($_[0], $ref);
1208 } else { 1737 } else {
1209 $self->_error (&Errno::EBADMSG); 1738 $self->_error (Errno::EBADMSG);
1210 } 1739 }
1211 }); 1740 });
1212 } 1741 }
1213 1742
1214 1 1743 1
1215 } 1744 }
1216}; 1745};
1217 1746
1218=back 1747=back
1219 1748
1220=item AnyEvent::Handle::register_read_type type => $coderef->($handle, $cb, @args) 1749=item custom read types - Package::anyevent_read_type $handle, $cb, @args
1221 1750
1222This function (not method) lets you add your own types to C<push_read>. 1751Instead of one of the predefined types, you can also specify the name
1752of a package. AnyEvent will try to load the package and then expects to
1753find a function named C<anyevent_read_type> inside. If it isn't found, it
1754progressively tries to load the parent package until it either finds the
1755function (good) or runs out of packages (bad).
1223 1756
1224Whenever the given C<type> is used, C<push_read> will invoke the code 1757Whenever this type is used, C<push_read> will invoke the function with the
1225reference with the handle object, the callback and the remaining 1758handle object, the original callback and the remaining arguments.
1226arguments.
1227 1759
1228The code reference is supposed to return a callback (usually a closure) 1760The function is supposed to return a callback (usually a closure) that
1229that works as a plain read callback (see C<< ->push_read ($cb) >>). 1761works as a plain read callback (see C<< ->push_read ($cb) >>), so you can
1762mentally treat the function as a "configurable read type to read callback"
1763converter.
1230 1764
1231It should invoke the passed callback when it is done reading (remember to 1765It should invoke the original callback when it is done reading (remember
1232pass C<$handle> as first argument as all other callbacks do that). 1766to pass C<$handle> as first argument as all other callbacks do that,
1767although there is no strict requirement on this).
1233 1768
1234Note that this is a function, and all types registered this way will be
1235global, so try to use unique names.
1236
1237For examples, see the source of this module (F<perldoc -m AnyEvent::Handle>, 1769For examples, see the source of this module (F<perldoc -m
1238search for C<register_read_type>)). 1770AnyEvent::Handle>, search for C<register_read_type>)).
1239 1771
1240=item $handle->stop_read 1772=item $handle->stop_read
1241 1773
1242=item $handle->start_read 1774=item $handle->start_read
1243 1775
1249Note that AnyEvent::Handle will automatically C<start_read> for you when 1781Note that AnyEvent::Handle will automatically C<start_read> for you when
1250you change the C<on_read> callback or push/unshift a read callback, and it 1782you change the C<on_read> callback or push/unshift a read callback, and it
1251will automatically C<stop_read> for you when neither C<on_read> is set nor 1783will automatically C<stop_read> for you when neither C<on_read> is set nor
1252there are any read requests in the queue. 1784there are any read requests in the queue.
1253 1785
1786In older versions of this module (<= 5.3), these methods had no effect,
1787as TLS does not support half-duplex connections. In current versions they
1788work as expected, as this behaviour is required to avoid certain resource
1789attacks, where the program would be forced to read (and buffer) arbitrary
1790amounts of data before being able to send some data. The drawback is that
1791some readings of the the SSL/TLS specifications basically require this
1792attack to be working, as SSL/TLS implementations might stall sending data
1793during a rehandshake.
1794
1795As a guideline, during the initial handshake, you should not stop reading,
1796and as a client, it might cause problems, depending on your applciation.
1797
1254=cut 1798=cut
1255 1799
1256sub stop_read { 1800sub stop_read {
1257 my ($self) = @_; 1801 my ($self) = @_;
1258 1802
1260} 1804}
1261 1805
1262sub start_read { 1806sub start_read {
1263 my ($self) = @_; 1807 my ($self) = @_;
1264 1808
1265 unless ($self->{_rw} || $self->{_eof}) { 1809 unless ($self->{_rw} || $self->{_eof} || !$self->{fh}) {
1266 Scalar::Util::weaken $self; 1810 Scalar::Util::weaken $self;
1267 1811
1268 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { 1812 $self->{_rw} = AE::io $self->{fh}, 0, sub {
1269 my $rbuf = $self->{filter_r} ? \my $buf : \$self->{rbuf}; 1813 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1270 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; 1814 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size}, length $$rbuf;
1271 1815
1272 if ($len > 0) { 1816 if ($len > 0) {
1273 $self->{_activity} = AnyEvent->now; 1817 $self->{_activity} = $self->{_ractivity} = AE::now;
1274 1818
1275 $self->{filter_r} 1819 if ($self->{tls}) {
1276 ? $self->{filter_r}($self, $rbuf) 1820 Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);
1277 : $self->{_in_drain} || $self->_drain_rbuf; 1821
1822 &_dotls ($self);
1823 } else {
1824 $self->_drain_rbuf;
1825 }
1826
1827 if ($len == $self->{read_size}) {
1828 $self->{read_size} *= 2;
1829 $self->{read_size} = $self->{max_read_size} || MAX_READ_SIZE
1830 if $self->{read_size} > ($self->{max_read_size} || MAX_READ_SIZE);
1831 }
1278 1832
1279 } elsif (defined $len) { 1833 } elsif (defined $len) {
1280 delete $self->{_rw}; 1834 delete $self->{_rw};
1281 $self->{_eof} = 1; 1835 $self->{_eof} = 1;
1282 $self->_drain_rbuf unless $self->{_in_drain}; 1836 $self->_drain_rbuf;
1283 1837
1284 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { 1838 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
1285 return $self->_error ($!, 1); 1839 return $self->_error ($!, 1);
1286 } 1840 }
1287 }); 1841 };
1288 } 1842 }
1289} 1843}
1290 1844
1845our $ERROR_SYSCALL;
1846our $ERROR_WANT_READ;
1847
1848sub _tls_error {
1849 my ($self, $err) = @_;
1850
1851 return $self->_error ($!, 1)
1852 if $err == Net::SSLeay::ERROR_SYSCALL ();
1853
1854 my $err =Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ());
1855
1856 # reduce error string to look less scary
1857 $err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /;
1858
1859 if ($self->{_on_starttls}) {
1860 (delete $self->{_on_starttls})->($self, undef, $err);
1861 &_freetls;
1862 } else {
1863 &_freetls;
1864 $self->_error (Errno::EPROTO, 1, $err);
1865 }
1866}
1867
1868# poll the write BIO and send the data if applicable
1869# also decode read data if possible
1870# this is basiclaly our TLS state machine
1871# more efficient implementations are possible with openssl,
1872# but not with the buggy and incomplete Net::SSLeay.
1291sub _dotls { 1873sub _dotls {
1292 my ($self) = @_; 1874 my ($self) = @_;
1293 1875
1294 my $buf; 1876 my $tmp;
1295 1877
1296 if (length $self->{_tls_wbuf}) { 1878 if (length $self->{_tls_wbuf}) {
1297 while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { 1879 while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {
1298 substr $self->{_tls_wbuf}, 0, $len, ""; 1880 substr $self->{_tls_wbuf}, 0, $tmp, "";
1299 } 1881 }
1300 }
1301 1882
1883 $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);
1884 return $self->_tls_error ($tmp)
1885 if $tmp != $ERROR_WANT_READ
1886 && ($tmp != $ERROR_SYSCALL || $!);
1887 }
1888
1889 while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
1890 unless (length $tmp) {
1891 $self->{_on_starttls}
1892 and (delete $self->{_on_starttls})->($self, undef, "EOF during handshake"); # ???
1893 &_freetls;
1894
1895 if ($self->{on_stoptls}) {
1896 $self->{on_stoptls}($self);
1897 return;
1898 } else {
1899 # let's treat SSL-eof as we treat normal EOF
1900 delete $self->{_rw};
1901 $self->{_eof} = 1;
1902 }
1903 }
1904
1905 $self->{_tls_rbuf} .= $tmp;
1906 $self->_drain_rbuf;
1907 $self->{tls} or return; # tls session might have gone away in callback
1908 }
1909
1910 $tmp = Net::SSLeay::get_error ($self->{tls}, -1);
1911 return $self->_tls_error ($tmp)
1912 if $tmp != $ERROR_WANT_READ
1913 && ($tmp != $ERROR_SYSCALL || $!);
1914
1302 if (length ($buf = Net::SSLeay::BIO_read ($self->{_wbio}))) { 1915 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
1303 $self->{wbuf} .= $buf; 1916 $self->{wbuf} .= $tmp;
1304 $self->_drain_wbuf; 1917 $self->_drain_wbuf;
1918 $self->{tls} or return; # tls session might have gone away in callback
1305 } 1919 }
1306 1920
1307 while (defined ($buf = Net::SSLeay::read ($self->{tls}))) { 1921 $self->{_on_starttls}
1308 if (length $buf) { 1922 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
1309 $self->{rbuf} .= $buf; 1923 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
1310 $self->_drain_rbuf unless $self->{_in_drain};
1311 } else {
1312 # let's treat SSL-eof as we treat normal EOF
1313 $self->{_eof} = 1;
1314 $self->_shutdown;
1315 return;
1316 }
1317 }
1318
1319 my $err = Net::SSLeay::get_error ($self->{tls}, -1);
1320
1321 if ($err!= Net::SSLeay::ERROR_WANT_READ ()) {
1322 if ($err == Net::SSLeay::ERROR_SYSCALL ()) {
1323 return $self->_error ($!, 1);
1324 } elsif ($err == Net::SSLeay::ERROR_SSL ()) {
1325 return $self->_error (&Errno::EIO, 1);
1326 }
1327
1328 # all others are fine for our purposes
1329 }
1330} 1924}
1331 1925
1332=item $handle->starttls ($tls[, $tls_ctx]) 1926=item $handle->starttls ($tls[, $tls_ctx])
1333 1927
1334Instead of starting TLS negotiation immediately when the AnyEvent::Handle 1928Instead of starting TLS negotiation immediately when the AnyEvent::Handle
1335object is created, you can also do that at a later time by calling 1929object is created, you can also do that at a later time by calling
1336C<starttls>. 1930C<starttls>.
1337 1931
1932Starting TLS is currently an asynchronous operation - when you push some
1933write data and then call C<< ->starttls >> then TLS negotiation will start
1934immediately, after which the queued write data is then sent.
1935
1338The first argument is the same as the C<tls> constructor argument (either 1936The first argument is the same as the C<tls> constructor argument (either
1339C<"connect">, C<"accept"> or an existing Net::SSLeay object). 1937C<"connect">, C<"accept"> or an existing Net::SSLeay object).
1340 1938
1341The second argument is the optional C<Net::SSLeay::CTX> object that is 1939The second argument is the optional C<AnyEvent::TLS> object that is used
1342used when AnyEvent::Handle has to create its own TLS connection object. 1940when AnyEvent::Handle has to create its own TLS connection object, or
1941a hash reference with C<< key => value >> pairs that will be used to
1942construct a new context.
1343 1943
1344The TLS connection object will end up in C<< $handle->{tls} >> after this 1944The TLS connection object will end up in C<< $handle->{tls} >>, the TLS
1345call and can be used or changed to your liking. Note that the handshake 1945context in C<< $handle->{tls_ctx} >> after this call and can be used or
1346might have already started when this function returns. 1946changed to your liking. Note that the handshake might have already started
1947when this function returns.
1347 1948
1949Due to bugs in OpenSSL, it might or might not be possible to do multiple
1950handshakes on the same stream. It is best to not attempt to use the
1951stream after stopping TLS.
1952
1953This method may invoke callbacks (and therefore the handle might be
1954destroyed after it returns).
1955
1348=cut 1956=cut
1957
1958our %TLS_CACHE; #TODO not yet documented, should we?
1349 1959
1350sub starttls { 1960sub starttls {
1351 my ($self, $ssl, $ctx) = @_; 1961 my ($self, $tls, $ctx) = @_;
1352 1962
1353 $self->stoptls; 1963 Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught"
1964 if $self->{tls};
1354 1965
1355 if ($ssl eq "accept") { 1966 $self->{tls} = $tls;
1356 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1967 $self->{tls_ctx} = $ctx if @_ > 2;
1357 Net::SSLeay::set_accept_state ($ssl); 1968
1358 } elsif ($ssl eq "connect") { 1969 return unless $self->{fh};
1359 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1970
1360 Net::SSLeay::set_connect_state ($ssl); 1971 require Net::SSLeay;
1972
1973 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
1974 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
1975
1976 $tls = delete $self->{tls};
1977 $ctx = $self->{tls_ctx};
1978
1979 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session
1980
1981 if ("HASH" eq ref $ctx) {
1982 require AnyEvent::TLS;
1983
1984 if ($ctx->{cache}) {
1985 my $key = $ctx+0;
1986 $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx;
1987 } else {
1988 $ctx = new AnyEvent::TLS %$ctx;
1989 }
1990 }
1361 } 1991
1362 1992 $self->{tls_ctx} = $ctx || TLS_CTX ();
1363 $self->{tls} = $ssl; 1993 $self->{tls} = $tls = $self->{tls_ctx}->_get_session ($tls, $self, $self->{peername});
1364 1994
1365 # basically, this is deep magic (because SSL_read should have the same issues) 1995 # basically, this is deep magic (because SSL_read should have the same issues)
1366 # but the openssl maintainers basically said: "trust us, it just works". 1996 # but the openssl maintainers basically said: "trust us, it just works".
1367 # (unfortunately, we have to hardcode constants because the abysmally misdesigned 1997 # (unfortunately, we have to hardcode constants because the abysmally misdesigned
1368 # and mismaintained ssleay-module doesn't even offer them). 1998 # and mismaintained ssleay-module doesn't even offer them).
1369 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html 1999 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html
2000 #
2001 # in short: this is a mess.
2002 #
2003 # note that we do not try to keep the length constant between writes as we are required to do.
2004 # we assume that most (but not all) of this insanity only applies to non-blocking cases,
2005 # and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to
2006 # have identity issues in that area.
1370 Net::SSLeay::CTX_set_mode ($self->{tls}, 2007# Net::SSLeay::CTX_set_mode ($ssl,
1371 (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) 2008# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
1372 | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); 2009# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
2010 Net::SSLeay::CTX_set_mode ($tls, 1|2);
1373 2011
1374 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 2012 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1375 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 2013 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1376 2014
2015 Net::SSLeay::BIO_write ($self->{_rbio}, $self->{rbuf});
2016 $self->{rbuf} = "";
2017
1377 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio}); 2018 Net::SSLeay::set_bio ($tls, $self->{_rbio}, $self->{_wbio});
1378 2019
1379 $self->{filter_w} = sub { 2020 $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }
1380 $_[0]{_tls_wbuf} .= ${$_[1]}; 2021 if $self->{on_starttls};
1381 &_dotls; 2022
1382 }; 2023 &_dotls; # need to trigger the initial handshake
1383 $self->{filter_r} = sub { 2024 $self->start_read; # make sure we actually do read
1384 Net::SSLeay::BIO_write ($_[0]{_rbio}, ${$_[1]});
1385 &_dotls;
1386 };
1387} 2025}
1388 2026
1389=item $handle->stoptls 2027=item $handle->stoptls
1390 2028
1391Destroys the SSL connection, if any. Partial read or write data will be 2029Shuts down the SSL connection - this makes a proper EOF handshake by
1392lost. 2030sending a close notify to the other side, but since OpenSSL doesn't
2031support non-blocking shut downs, it is not guaranteed that you can re-use
2032the stream afterwards.
2033
2034This method may invoke callbacks (and therefore the handle might be
2035destroyed after it returns).
1393 2036
1394=cut 2037=cut
1395 2038
1396sub stoptls { 2039sub stoptls {
1397 my ($self) = @_; 2040 my ($self) = @_;
1398 2041
1399 Net::SSLeay::free (delete $self->{tls}) if $self->{tls}; 2042 if ($self->{tls} && $self->{fh}) {
2043 Net::SSLeay::shutdown ($self->{tls});
1400 2044
1401 delete $self->{_rbio}; 2045 &_dotls;
1402 delete $self->{_wbio}; 2046
1403 delete $self->{_tls_wbuf}; 2047# # we don't give a shit. no, we do, but we can't. no...#d#
1404 delete $self->{filter_r}; 2048# # we, we... have to use openssl :/#d#
1405 delete $self->{filter_w}; 2049# &_freetls;#d#
2050 }
1406} 2051}
2052
2053sub _freetls {
2054 my ($self) = @_;
2055
2056 return unless $self->{tls};
2057
2058 $self->{tls_ctx}->_put_session (delete $self->{tls})
2059 if $self->{tls} > 0;
2060
2061 delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)};
2062}
2063
2064=item $handle->resettls
2065
2066This rarely-used method simply resets and TLS state on the handle, usually
2067causing data loss.
2068
2069One case where it may be useful is when you want to skip over the data in
2070the stream but you are not interested in interpreting it, so data loss is
2071no concern.
2072
2073=cut
2074
2075*resettls = \&_freetls;
1407 2076
1408sub DESTROY { 2077sub DESTROY {
1409 my $self = shift; 2078 my ($self) = @_;
1410 2079
1411 $self->stoptls; 2080 &_freetls;
1412 2081
1413 my $linger = exists $self->{linger} ? $self->{linger} : 3600; 2082 my $linger = exists $self->{linger} ? $self->{linger} : 3600;
1414 2083
1415 if ($linger && length $self->{wbuf}) { 2084 if ($linger && length $self->{wbuf} && $self->{fh}) {
1416 my $fh = delete $self->{fh}; 2085 my $fh = delete $self->{fh};
1417 my $wbuf = delete $self->{wbuf}; 2086 my $wbuf = delete $self->{wbuf};
1418 2087
1419 my @linger; 2088 my @linger;
1420 2089
1421 push @linger, AnyEvent->io (fh => $fh, poll => "w", cb => sub { 2090 push @linger, AE::io $fh, 1, sub {
1422 my $len = syswrite $fh, $wbuf, length $wbuf; 2091 my $len = syswrite $fh, $wbuf, length $wbuf;
1423 2092
1424 if ($len > 0) { 2093 if ($len > 0) {
1425 substr $wbuf, 0, $len, ""; 2094 substr $wbuf, 0, $len, "";
1426 } else { 2095 } elsif (defined $len || ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK)) {
1427 @linger = (); # end 2096 @linger = (); # end
1428 } 2097 }
2098 };
2099 push @linger, AE::timer $linger, 0, sub {
2100 @linger = ();
2101 };
2102 }
2103}
2104
2105=item $handle->destroy
2106
2107Shuts down the handle object as much as possible - this call ensures that
2108no further callbacks will be invoked and as many resources as possible
2109will be freed. Any method you will call on the handle object after
2110destroying it in this way will be silently ignored (and it will return the
2111empty list).
2112
2113Normally, you can just "forget" any references to an AnyEvent::Handle
2114object and it will simply shut down. This works in fatal error and EOF
2115callbacks, as well as code outside. It does I<NOT> work in a read or write
2116callback, so when you want to destroy the AnyEvent::Handle object from
2117within such an callback. You I<MUST> call C<< ->destroy >> explicitly in
2118that case.
2119
2120Destroying the handle object in this way has the advantage that callbacks
2121will be removed as well, so if those are the only reference holders (as
2122is common), then one doesn't need to do anything special to break any
2123reference cycles.
2124
2125The handle might still linger in the background and write out remaining
2126data, as specified by the C<linger> option, however.
2127
2128=cut
2129
2130sub destroy {
2131 my ($self) = @_;
2132
2133 $self->DESTROY;
2134 %$self = ();
2135 bless $self, "AnyEvent::Handle::destroyed";
2136}
2137
2138sub AnyEvent::Handle::destroyed::AUTOLOAD {
2139 #nop
2140}
2141
2142=item $handle->destroyed
2143
2144Returns false as long as the handle hasn't been destroyed by a call to C<<
2145->destroy >>, true otherwise.
2146
2147Can be useful to decide whether the handle is still valid after some
2148callback possibly destroyed the handle. For example, C<< ->push_write >>,
2149C<< ->starttls >> and other methods can call user callbacks, which in turn
2150can destroy the handle, so work can be avoided by checking sometimes:
2151
2152 $hdl->starttls ("accept");
2153 return if $hdl->destroyed;
2154 $hdl->push_write (...
2155
2156Note that the call to C<push_write> will silently be ignored if the handle
2157has been destroyed, so often you can just ignore the possibility of the
2158handle being destroyed.
2159
2160=cut
2161
2162sub destroyed { 0 }
2163sub AnyEvent::Handle::destroyed::destroyed { 1 }
2164
2165=item AnyEvent::Handle::TLS_CTX
2166
2167This function creates and returns the AnyEvent::TLS object used by default
2168for TLS mode.
2169
2170The context is created by calling L<AnyEvent::TLS> without any arguments.
2171
2172=cut
2173
2174our $TLS_CTX;
2175
2176sub TLS_CTX() {
2177 $TLS_CTX ||= do {
2178 require AnyEvent::TLS;
2179
2180 new AnyEvent::TLS
2181 }
2182}
2183
2184=back
2185
2186
2187=head1 NONFREQUENTLY ASKED QUESTIONS
2188
2189=over 4
2190
2191=item I C<undef> the AnyEvent::Handle reference inside my callback and
2192still get further invocations!
2193
2194That's because AnyEvent::Handle keeps a reference to itself when handling
2195read or write callbacks.
2196
2197It is only safe to "forget" the reference inside EOF or error callbacks,
2198from within all other callbacks, you need to explicitly call the C<<
2199->destroy >> method.
2200
2201=item Why is my C<on_eof> callback never called?
2202
2203Probably because your C<on_error> callback is being called instead: When
2204you have outstanding requests in your read queue, then an EOF is
2205considered an error as you clearly expected some data.
2206
2207To avoid this, make sure you have an empty read queue whenever your handle
2208is supposed to be "idle" (i.e. connection closes are O.K.). You cna set
2209an C<on_read> handler that simply pushes the first read requests in the
2210queue.
2211
2212See also the next question, which explains this in a bit more detail.
2213
2214=item How can I serve requests in a loop?
2215
2216Most protocols consist of some setup phase (authentication for example)
2217followed by a request handling phase, where the server waits for requests
2218and handles them, in a loop.
2219
2220There are two important variants: The first (traditional, better) variant
2221handles requests until the server gets some QUIT command, causing it to
2222close the connection first (highly desirable for a busy TCP server). A
2223client dropping the connection is an error, which means this variant can
2224detect an unexpected detection close.
2225
2226To handle this case, always make sure you have a on-empty read queue, by
2227pushing the "read request start" handler on it:
2228
2229 # we assume a request starts with a single line
2230 my @start_request; @start_request = (line => sub {
2231 my ($hdl, $line) = @_;
2232
2233 ... handle request
2234
2235 # push next request read, possibly from a nested callback
2236 $hdl->push_read (@start_request);
2237 });
2238
2239 # auth done, now go into request handling loop
2240 # now push the first @start_request
2241 $hdl->push_read (@start_request);
2242
2243By always having an outstanding C<push_read>, the handle always expects
2244some data and raises the C<EPIPE> error when the connction is dropped
2245unexpectedly.
2246
2247The second variant is a protocol where the client can drop the connection
2248at any time. For TCP, this means that the server machine may run out of
2249sockets easier, and in general, it means you cnanot distinguish a protocl
2250failure/client crash from a normal connection close. Nevertheless, these
2251kinds of protocols are common (and sometimes even the best solution to the
2252problem).
2253
2254Having an outstanding read request at all times is possible if you ignore
2255C<EPIPE> errors, but this doesn't help with when the client drops the
2256connection during a request, which would still be an error.
2257
2258A better solution is to push the initial request read in an C<on_read>
2259callback. This avoids an error, as when the server doesn't expect data
2260(i.e. is idly waiting for the next request, an EOF will not raise an
2261error, but simply result in an C<on_eof> callback. It is also a bit slower
2262and simpler:
2263
2264 # auth done, now go into request handling loop
2265 $hdl->on_read (sub {
2266 my ($hdl) = @_;
2267
2268 # called each time we receive data but the read queue is empty
2269 # simply start read the request
2270
2271 $hdl->push_read (line => sub {
2272 my ($hdl, $line) = @_;
2273
2274 ... handle request
2275
2276 # do nothing special when the request has been handled, just
2277 # let the request queue go empty.
1429 }); 2278 });
1430 push @linger, AnyEvent->timer (after => $linger, cb => sub {
1431 @linger = ();
1432 }); 2279 });
2280
2281=item I get different callback invocations in TLS mode/Why can't I pause
2282reading?
2283
2284Unlike, say, TCP, TLS connections do not consist of two independent
2285communication channels, one for each direction. Or put differently, the
2286read and write directions are not independent of each other: you cannot
2287write data unless you are also prepared to read, and vice versa.
2288
2289This means that, in TLS mode, you might get C<on_error> or C<on_eof>
2290callback invocations when you are not expecting any read data - the reason
2291is that AnyEvent::Handle always reads in TLS mode.
2292
2293During the connection, you have to make sure that you always have a
2294non-empty read-queue, or an C<on_read> watcher. At the end of the
2295connection (or when you no longer want to use it) you can call the
2296C<destroy> method.
2297
2298=item How do I read data until the other side closes the connection?
2299
2300If you just want to read your data into a perl scalar, the easiest way
2301to achieve this is by setting an C<on_read> callback that does nothing,
2302clearing the C<on_eof> callback and in the C<on_error> callback, the data
2303will be in C<$_[0]{rbuf}>:
2304
2305 $handle->on_read (sub { });
2306 $handle->on_eof (undef);
2307 $handle->on_error (sub {
2308 my $data = delete $_[0]{rbuf};
2309 });
2310
2311Note that this example removes the C<rbuf> member from the handle object,
2312which is not normally allowed by the API. It is expressly permitted in
2313this case only, as the handle object needs to be destroyed afterwards.
2314
2315The reason to use C<on_error> is that TCP connections, due to latencies
2316and packets loss, might get closed quite violently with an error, when in
2317fact all data has been received.
2318
2319It is usually better to use acknowledgements when transferring data,
2320to make sure the other side hasn't just died and you got the data
2321intact. This is also one reason why so many internet protocols have an
2322explicit QUIT command.
2323
2324=item I don't want to destroy the handle too early - how do I wait until
2325all data has been written?
2326
2327After writing your last bits of data, set the C<on_drain> callback
2328and destroy the handle in there - with the default setting of
2329C<low_water_mark> this will be called precisely when all data has been
2330written to the socket:
2331
2332 $handle->push_write (...);
2333 $handle->on_drain (sub {
2334 warn "all data submitted to the kernel\n";
2335 undef $handle;
2336 });
2337
2338If you just want to queue some data and then signal EOF to the other side,
2339consider using C<< ->push_shutdown >> instead.
2340
2341=item I want to contact a TLS/SSL server, I don't care about security.
2342
2343If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS,
2344connect to it and then create the AnyEvent::Handle with the C<tls>
2345parameter:
2346
2347 tcp_connect $host, $port, sub {
2348 my ($fh) = @_;
2349
2350 my $handle = new AnyEvent::Handle
2351 fh => $fh,
2352 tls => "connect",
2353 on_error => sub { ... };
2354
2355 $handle->push_write (...);
1433 } 2356 };
1434}
1435 2357
1436=item AnyEvent::Handle::TLS_CTX 2358=item I want to contact a TLS/SSL server, I do care about security.
1437 2359
1438This function creates and returns the Net::SSLeay::CTX object used by 2360Then you should additionally enable certificate verification, including
1439default for TLS mode. 2361peername verification, if the protocol you use supports it (see
2362L<AnyEvent::TLS>, C<verify_peername>).
1440 2363
1441The context is created like this: 2364E.g. for HTTPS:
1442 2365
1443 Net::SSLeay::load_error_strings; 2366 tcp_connect $host, $port, sub {
1444 Net::SSLeay::SSLeay_add_ssl_algorithms; 2367 my ($fh) = @_;
1445 Net::SSLeay::randomize;
1446 2368
1447 my $CTX = Net::SSLeay::CTX_new; 2369 my $handle = new AnyEvent::Handle
2370 fh => $fh,
2371 peername => $host,
2372 tls => "connect",
2373 tls_ctx => { verify => 1, verify_peername => "https" },
2374 ...
1448 2375
1449 Net::SSLeay::CTX_set_options $CTX, Net::SSLeay::OP_ALL 2376Note that you must specify the hostname you connected to (or whatever
2377"peername" the protocol needs) as the C<peername> argument, otherwise no
2378peername verification will be done.
1450 2379
1451=cut 2380The above will use the system-dependent default set of trusted CA
2381certificates. If you want to check against a specific CA, add the
2382C<ca_file> (or C<ca_cert>) arguments to C<tls_ctx>:
1452 2383
1453our $TLS_CTX; 2384 tls_ctx => {
2385 verify => 1,
2386 verify_peername => "https",
2387 ca_file => "my-ca-cert.pem",
2388 },
1454 2389
1455sub TLS_CTX() { 2390=item I want to create a TLS/SSL server, how do I do that?
1456 $TLS_CTX || do {
1457 require Net::SSLeay;
1458 2391
1459 Net::SSLeay::load_error_strings (); 2392Well, you first need to get a server certificate and key. You have
1460 Net::SSLeay::SSLeay_add_ssl_algorithms (); 2393three options: a) ask a CA (buy one, use cacert.org etc.) b) create a
1461 Net::SSLeay::randomize (); 2394self-signed certificate (cheap. check the search engine of your choice,
2395there are many tutorials on the net) or c) make your own CA (tinyca2 is a
2396nice program for that purpose).
1462 2397
1463 $TLS_CTX = Net::SSLeay::CTX_new (); 2398Then create a file with your private key (in PEM format, see
2399L<AnyEvent::TLS>), followed by the certificate (also in PEM format). The
2400file should then look like this:
1464 2401
1465 Net::SSLeay::CTX_set_options ($TLS_CTX, Net::SSLeay::OP_ALL ()); 2402 -----BEGIN RSA PRIVATE KEY-----
2403 ...header data
2404 ... lots of base64'y-stuff
2405 -----END RSA PRIVATE KEY-----
1466 2406
1467 $TLS_CTX 2407 -----BEGIN CERTIFICATE-----
1468 } 2408 ... lots of base64'y-stuff
1469} 2409 -----END CERTIFICATE-----
2410
2411The important bits are the "PRIVATE KEY" and "CERTIFICATE" parts. Then
2412specify this file as C<cert_file>:
2413
2414 tcp_server undef, $port, sub {
2415 my ($fh) = @_;
2416
2417 my $handle = new AnyEvent::Handle
2418 fh => $fh,
2419 tls => "accept",
2420 tls_ctx => { cert_file => "my-server-keycert.pem" },
2421 ...
2422
2423When you have intermediate CA certificates that your clients might not
2424know about, just append them to the C<cert_file>.
1470 2425
1471=back 2426=back
2427
1472 2428
1473=head1 SUBCLASSING AnyEvent::Handle 2429=head1 SUBCLASSING AnyEvent::Handle
1474 2430
1475In many cases, you might want to subclass AnyEvent::Handle. 2431In many cases, you might want to subclass AnyEvent::Handle.
1476 2432
1493 2449
1494=item * all members not documented here and not prefixed with an underscore 2450=item * all members not documented here and not prefixed with an underscore
1495are free to use in subclasses. 2451are free to use in subclasses.
1496 2452
1497Of course, new versions of AnyEvent::Handle may introduce more "public" 2453Of course, new versions of AnyEvent::Handle may introduce more "public"
1498member variables, but thats just life, at least it is documented. 2454member variables, but that's just life. At least it is documented.
1499 2455
1500=back 2456=back
1501 2457
1502=head1 AUTHOR 2458=head1 AUTHOR
1503 2459

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines