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.85 by root, Thu Aug 21 19:53:19 2008 UTC vs.
Revision 1.149 by root, Thu Jul 16 03:48:33 2009 UTC

14 14
15AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent 15AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent
16 16
17=cut 17=cut
18 18
19our $VERSION = 4.232; 19our $VERSION = 4.82;
20 20
21=head1 SYNOPSIS 21=head1 SYNOPSIS
22 22
23 use AnyEvent; 23 use AnyEvent;
24 use AnyEvent::Handle; 24 use AnyEvent::Handle;
25 25
26 my $cv = AnyEvent->condvar; 26 my $cv = AnyEvent->condvar;
27 27
28 my $handle = 28 my $hdl; $hdl = new AnyEvent::Handle
29 AnyEvent::Handle->new (
30 fh => \*STDIN, 29 fh => \*STDIN,
31 on_eof => sub { 30 on_error => sub {
32 $cv->broadcast; 31 warn "got error $_[2]\n";
33 }, 32 $cv->send;
34 ); 33 );
35 34
36 # send some request line 35 # send some request line
37 $handle->push_write ("getinfo\015\012"); 36 $hdl->push_write ("getinfo\015\012");
38 37
39 # read the response line 38 # read the response line
40 $handle->push_read (line => sub { 39 $hdl->push_read (line => sub {
41 my ($handle, $line) = @_; 40 my ($hdl, $line) = @_;
42 warn "read line <$line>\n"; 41 warn "got line <$line>\n";
43 $cv->send; 42 $cv->send;
44 }); 43 });
45 44
46 $cv->recv; 45 $cv->recv;
47 46
63 62
64=head1 METHODS 63=head1 METHODS
65 64
66=over 4 65=over 4
67 66
68=item B<new (%args)> 67=item $handle = B<new> AnyEvent::TLS fh => $filehandle, key => value...
69 68
70The constructor supports these arguments (all as key => value pairs). 69The constructor supports these arguments (all as C<< key => value >> pairs).
71 70
72=over 4 71=over 4
73 72
74=item fh => $filehandle [MANDATORY] 73=item fh => $filehandle [MANDATORY]
75 74
84Set the callback to be called when an end-of-file condition is detected, 83Set the callback to be called when an end-of-file condition is detected,
85i.e. in the case of a socket, when the other side has closed the 84i.e. in the case of a socket, when the other side has closed the
86connection cleanly. 85connection cleanly.
87 86
88For sockets, this just means that the other side has stopped sending data, 87For sockets, this just means that the other side has stopped sending data,
89you can still try to write data, and, in fact, one can return from the eof 88you can still try to write data, and, in fact, one can return from the EOF
90callback and continue writing data, as only the read part has been shut 89callback and continue writing data, as only the read part has been shut
91down. 90down.
92 91
93While not mandatory, it is I<highly> recommended to set an eof callback, 92While not mandatory, it is I<highly> recommended to set an EOF callback,
94otherwise you might end up with a closed socket while you are still 93otherwise you might end up with a closed socket while you are still
95waiting for data. 94waiting for data.
96 95
97If an EOF condition has been detected but no C<on_eof> callback has been 96If an EOF condition has been detected but no C<on_eof> callback has been
98set, then a fatal error will be raised with C<$!> set to <0>. 97set, then a fatal error will be raised with C<$!> set to <0>.
99 98
100=item on_error => $cb->($handle, $fatal) 99=item on_error => $cb->($handle, $fatal, $message)
101 100
102This is the error callback, which is called when, well, some error 101This is the error callback, which is called when, well, some error
103occured, such as not being able to resolve the hostname, failure to 102occured, such as not being able to resolve the hostname, failure to
104connect or a read error. 103connect or a read error.
105 104
106Some errors are fatal (which is indicated by C<$fatal> being true). On 105Some 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 106fatal 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 107destroy >>) after invoking the error callback (which means you are free to
109errors are an EOF condition with active (but unsatisifable) read watchers 108examine the handle object). Examples of fatal errors are an EOF condition
110(C<EPIPE>) or I/O errors. 109with active (but unsatisifable) read watchers (C<EPIPE>) or I/O errors.
110
111AnyEvent::Handle tries to find an appropriate error code for you to check
112against, but in some cases (TLS errors), this does not work well. It is
113recommended to always output the C<$message> argument in human-readable
114error messages (it's usually the same as C<"$!">).
111 115
112Non-fatal errors can be retried by simply returning, but it is recommended 116Non-fatal errors can be retried by simply returning, but it is recommended
113to simply ignore this parameter and instead abondon the handle object 117to simply ignore this parameter and instead abondon the handle object
114when this callback is invoked. Examples of non-fatal errors are timeouts 118when this callback is invoked. Examples of non-fatal errors are timeouts
115C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>). 119C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
116 120
117On callback entrance, the value of C<$!> contains the operating system 121On callback entrance, the value of C<$!> contains the operating system
118error (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT> or C<EBADMSG>). 122error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or
123C<EPROTO>).
119 124
120While not mandatory, it is I<highly> recommended to set this callback, as 125While not mandatory, it is I<highly> recommended to set this callback, as
121you will not be notified of errors otherwise. The default simply calls 126you will not be notified of errors otherwise. The default simply calls
122C<croak>. 127C<croak>.
123 128
127and no read request is in the queue (unlike read queue callbacks, this 132and 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 133callback will only be called when at least one octet of data is in the
129read buffer). 134read buffer).
130 135
131To access (and remove data from) the read buffer, use the C<< ->rbuf >> 136To access (and remove data from) the read buffer, use the C<< ->rbuf >>
132method or access the C<$handle->{rbuf}> member directly. 137method or access the C<< $handle->{rbuf} >> member directly. Note that you
138must not enlarge or modify the read buffer, you can only remove data at
139the beginning from it.
133 140
134When an EOF condition is detected then AnyEvent::Handle will first try to 141When an EOF condition is detected then AnyEvent::Handle will first try to
135feed all the remaining data to the queued callbacks and C<on_read> before 142feed 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 143calling the C<on_eof> callback. If no progress can be made, then a fatal
137error will be raised (with C<$!> set to C<EPIPE>). 144error will be raised (with C<$!> set to C<EPIPE>).
152=item timeout => $fractional_seconds 159=item timeout => $fractional_seconds
153 160
154If non-zero, then this enables an "inactivity" timeout: whenever this many 161If non-zero, then this enables an "inactivity" timeout: whenever this many
155seconds pass without a successful read or write on the underlying file 162seconds pass without a successful read or write on the underlying file
156handle, the C<on_timeout> callback will be invoked (and if that one is 163handle, the C<on_timeout> callback will be invoked (and if that one is
157missing, an C<ETIMEDOUT> error will be raised). 164missing, a non-fatal C<ETIMEDOUT> error will be raised).
158 165
159Note that timeout processing is also active when you currently do not have 166Note that timeout processing is also active when you currently do not have
160any outstanding read or write requests: If you plan to keep the connection 167any outstanding read or write requests: If you plan to keep the connection
161idle then you should disable the timout temporarily or ignore the timeout 168idle then you should disable the timout temporarily or ignore the timeout
162in the C<on_timeout> callback. 169in the C<on_timeout> callback, in which case AnyEvent::Handle will simply
170restart the timeout.
163 171
164Zero (the default) disables this timeout. 172Zero (the default) disables this timeout.
165 173
166=item on_timeout => $cb->($handle) 174=item on_timeout => $cb->($handle)
167 175
171 179
172=item rbuf_max => <bytes> 180=item rbuf_max => <bytes>
173 181
174If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>) 182If 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 183when the read buffer ever (strictly) exceeds this size. This is useful to
176avoid denial-of-service attacks. 184avoid some forms of denial-of-service attacks.
177 185
178For example, a server accepting connections from untrusted sources should 186For example, a server accepting connections from untrusted sources should
179be configured to accept only so-and-so much data that it cannot act on 187be 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 188(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 189amount of data without a callback ever being called as long as the line
182isn't finished). 190isn't finished).
183 191
184=item autocork => <boolean> 192=item autocork => <boolean>
185 193
186When disabled (the default), then C<push_write> will try to immediately 194When disabled (the default), then C<push_write> will try to immediately
187write the data to the handle if possible. This avoids having to register 195write 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 196a write watcher and wait for the next event loop iteration, but can
189inefficient if you write multiple small chunks (this disadvantage is 197be inefficient if you write multiple small chunks (on the wire, this
190usually avoided by your kernel's nagle algorithm, see C<low_delay>). 198disadvantage is usually avoided by your kernel's nagle algorithm, see
199C<no_delay>, but this option can save costly syscalls).
191 200
192When enabled, then writes will always be queued till the next event loop 201When enabled, then writes will always be queued till the next event loop
193iteration. This is efficient when you do many small writes per iteration, 202iteration. This is efficient when you do many small writes per iteration,
194but less efficient when you do a single write only. 203but less efficient when you do a single write only per iteration (or when
204the write buffer often is full). It also increases write latency.
195 205
196=item no_delay => <boolean> 206=item no_delay => <boolean>
197 207
198When doing small writes on sockets, your operating system kernel might 208When doing small writes on sockets, your operating system kernel might
199wait a bit for more data before actually sending it out. This is called 209wait a bit for more data before actually sending it out. This is called
200the Nagle algorithm, and usually it is beneficial. 210the Nagle algorithm, and usually it is beneficial.
201 211
202In some situations you want as low a delay as possible, which cna be 212In some situations you want as low a delay as possible, which can be
203accomplishd by setting this option to true. 213accomplishd by setting this option to a true value.
204 214
205The default is your opertaing system's default behaviour, this option 215The default is your opertaing system's default behaviour (most likely
206explicitly enables or disables it, if possible. 216enabled), this option explicitly enables or disables it, if possible.
207 217
208=item read_size => <bytes> 218=item read_size => <bytes>
209 219
210The default read block size (the amount of bytes this module will try to read 220The default read block size (the amount of bytes this module will
211during each (loop iteration). Default: C<8192>. 221try to read during each loop iteration, which affects memory
222requirements). Default: C<8192>.
212 223
213=item low_water_mark => <bytes> 224=item low_water_mark => <bytes>
214 225
215Sets the amount of bytes (default: C<0>) that make up an "empty" write 226Sets the amount of bytes (default: C<0>) that make up an "empty" write
216buffer: If the write reaches this size or gets even samller it is 227buffer: If the write reaches this size or gets even samller it is
217considered empty. 228considered empty.
218 229
230Sometimes it can be beneficial (for performance reasons) to add data to
231the write buffer before it is fully drained, but this is a rare case, as
232the operating system kernel usually buffers data as well, so the default
233is good in almost all cases.
234
219=item linger => <seconds> 235=item linger => <seconds>
220 236
221If non-zero (default: C<3600>), then the destructor of the 237If non-zero (default: C<3600>), then the destructor of the
222AnyEvent::Handle object will check wether there is still outstanding write 238AnyEvent::Handle object will check whether there is still outstanding
223data and will install a watcher that will write out this data. No errors 239write data and will install a watcher that will write this data to the
224will be reported (this mostly matches how the operating system treats 240socket. No errors will be reported (this mostly matches how the operating
225outstanding data at socket close time). 241system treats outstanding data at socket close time).
226 242
227This will not work for partial TLS data that could not yet been 243This will not work for partial TLS data that could not be encoded
228encoded. This data will be lost. 244yet. This data will be lost. Calling the C<stoptls> method in time might
245help.
246
247=item peername => $string
248
249A string used to identify the remote site - usually the DNS hostname
250(I<not> IDN!) used to create the connection, rarely the IP address.
251
252Apart from being useful in error messages, this string is also used in TLS
253peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This
254verification will be skipped when C<peername> is not specified or
255C<undef>.
229 256
230=item tls => "accept" | "connect" | Net::SSLeay::SSL object 257=item tls => "accept" | "connect" | Net::SSLeay::SSL object
231 258
232When this parameter is given, it enables TLS (SSL) mode, that means 259When this parameter is given, it enables TLS (SSL) mode, that means
233AnyEvent will start a TLS handshake and will transparently encrypt/decrypt 260AnyEvent will start a TLS handshake as soon as the conenction has been
234data. 261established and will transparently encrypt/decrypt data afterwards.
262
263All TLS protocol errors will be signalled as C<EPROTO>, with an
264appropriate error message.
235 265
236TLS mode requires Net::SSLeay to be installed (it will be loaded 266TLS mode requires Net::SSLeay to be installed (it will be loaded
237automatically when you try to create a TLS handle). 267automatically when you try to create a TLS handle): this module doesn't
268have a dependency on that module, so if your module requires it, you have
269to add the dependency yourself.
238 270
239Unlike TCP, TLS has a server and client side: for the TLS server side, use 271Unlike TCP, TLS has a server and client side: for the TLS server side, use
240C<accept>, and for the TLS client side of a connection, use C<connect> 272C<accept>, and for the TLS client side of a connection, use C<connect>
241mode. 273mode.
242 274
243You can also provide your own TLS connection object, but you have 275You can also provide your own TLS connection object, but you have
244to make sure that you call either C<Net::SSLeay::set_connect_state> 276to make sure that you call either C<Net::SSLeay::set_connect_state>
245or C<Net::SSLeay::set_accept_state> on it before you pass it to 277or C<Net::SSLeay::set_accept_state> on it before you pass it to
246AnyEvent::Handle. 278AnyEvent::Handle. Also, this module will take ownership of this connection
279object.
247 280
281At some future point, AnyEvent::Handle might switch to another TLS
282implementation, then the option to use your own session object will go
283away.
284
285B<IMPORTANT:> since Net::SSLeay "objects" are really only integers,
286passing in the wrong integer will lead to certain crash. This most often
287happens when one uses a stylish C<< tls => 1 >> and is surprised about the
288segmentation fault.
289
248See the C<starttls> method for when need to start TLS negotiation later. 290See the C<< ->starttls >> method for when need to start TLS negotiation later.
249 291
250=item tls_ctx => $ssl_ctx 292=item tls_ctx => $anyevent_tls
251 293
252Use the given Net::SSLeay::CTX object to create the new TLS connection 294Use the given C<AnyEvent::TLS> object to create the new TLS connection
253(unless a connection object was specified directly). If this parameter is 295(unless a connection object was specified directly). If this parameter is
254missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. 296missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>.
255 297
298Instead of an object, you can also specify a hash reference with C<< key
299=> value >> pairs. Those will be passed to L<AnyEvent::TLS> to create a
300new TLS context object.
301
302=item on_starttls => $cb->($handle, $success[, $error_message])
303
304This callback will be invoked when the TLS/SSL handshake has finished. If
305C<$success> is true, then the TLS handshake succeeded, otherwise it failed
306(C<on_stoptls> will not be called in this case).
307
308The session in C<< $handle->{tls} >> can still be examined in this
309callback, even when the handshake was not successful.
310
311TLS handshake failures will not cause C<on_error> to be invoked when this
312callback is in effect, instead, the error message will be passed to C<on_starttls>.
313
314Without this callback, handshake failures lead to C<on_error> being
315called, as normal.
316
317Note that you cannot call C<starttls> right again in this callback. If you
318need to do that, start an zero-second timer instead whose callback can
319then call C<< ->starttls >> again.
320
321=item on_stoptls => $cb->($handle)
322
323When a SSLv3/TLS shutdown/close notify/EOF is detected and this callback is
324set, then it will be invoked after freeing the TLS session. If it is not,
325then a TLS shutdown condition will be treated like a normal EOF condition
326on the handle.
327
328The session in C<< $handle->{tls} >> can still be examined in this
329callback.
330
331This callback will only be called on TLS shutdowns, not when the
332underlying handle signals EOF.
333
256=item json => JSON or JSON::XS object 334=item json => JSON or JSON::XS object
257 335
258This is the json coder object used by the C<json> read and write types. 336This is the json coder object used by the C<json> read and write types.
259 337
260If you don't supply it, then AnyEvent::Handle will create and use a 338If you don't supply it, then AnyEvent::Handle will create and use a
261suitable one, which will write and expect UTF-8 encoded JSON texts. 339suitable one (on demand), which will write and expect UTF-8 encoded JSON
340texts.
262 341
263Note that you are responsible to depend on the JSON module if you want to 342Note that you are responsible to depend on the JSON module if you want to
264use this functionality, as AnyEvent does not have a dependency itself. 343use this functionality, as AnyEvent does not have a dependency itself.
265 344
266=item filter_r => $cb
267
268=item filter_w => $cb
269
270These exist, but are undocumented at this time.
271
272=back 345=back
273 346
274=cut 347=cut
275 348
276sub new { 349sub new {
277 my $class = shift; 350 my $class = shift;
278
279 my $self = bless { @_ }, $class; 351 my $self = bless { @_ }, $class;
280 352
281 $self->{fh} or Carp::croak "mandatory argument fh is missing"; 353 $self->{fh} or Carp::croak "mandatory argument fh is missing";
282 354
283 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 355 AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
284
285 if ($self->{tls}) {
286 require Net::SSLeay;
287 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx});
288 }
289 356
290 $self->{_activity} = AnyEvent->now; 357 $self->{_activity} = AnyEvent->now;
291 $self->_timeout; 358 $self->_timeout;
292 359
293 $self->on_drain (delete $self->{on_drain}) if exists $self->{on_drain};
294 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay}; 360 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay};
361
362 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
363 if $self->{tls};
364
365 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain};
295 366
296 $self->start_read 367 $self->start_read
297 if $self->{on_read}; 368 if $self->{on_read};
298 369
299 $self 370 $self->{fh} && $self
300} 371}
301 372
302sub _shutdown { 373#sub _shutdown {
303 my ($self) = @_; 374# my ($self) = @_;
304 375#
305 delete $self->{_tw}; 376# delete @$self{qw(_tw _rw _ww fh wbuf on_read _queue)};
306 delete $self->{_rw}; 377# $self->{_eof} = 1; # tell starttls et. al to stop trying
307 delete $self->{_ww}; 378#
308 delete $self->{fh}; 379# &_freetls;
309 380#}
310 $self->stoptls;
311
312 delete $self->{on_read};
313 delete $self->{_queue};
314}
315 381
316sub _error { 382sub _error {
317 my ($self, $errno, $fatal) = @_; 383 my ($self, $errno, $fatal, $message) = @_;
318
319 $self->_shutdown
320 if $fatal;
321 384
322 $! = $errno; 385 $! = $errno;
386 $message ||= "$!";
323 387
324 if ($self->{on_error}) { 388 if ($self->{on_error}) {
325 $self->{on_error}($self, $fatal); 389 $self->{on_error}($self, $fatal, $message);
326 } else { 390 $self->destroy;
391 } elsif ($self->{fh}) {
392 $self->destroy;
327 Carp::croak "AnyEvent::Handle uncaught error: $!"; 393 Carp::croak "AnyEvent::Handle uncaught error: $message";
328 } 394 }
329} 395}
330 396
331=item $fh = $handle->fh 397=item $fh = $handle->fh
332 398
333This method returns the file handle of the L<AnyEvent::Handle> object. 399This method returns the file handle used to create the L<AnyEvent::Handle> object.
334 400
335=cut 401=cut
336 402
337sub fh { $_[0]{fh} } 403sub fh { $_[0]{fh} }
338 404
356 $_[0]{on_eof} = $_[1]; 422 $_[0]{on_eof} = $_[1];
357} 423}
358 424
359=item $handle->on_timeout ($cb) 425=item $handle->on_timeout ($cb)
360 426
361Replace the current C<on_timeout> callback, or disables the callback 427Replace the current C<on_timeout> callback, or disables the callback (but
362(but not the timeout) if C<$cb> = C<undef>. See C<timeout> constructor 428not the timeout) if C<$cb> = C<undef>. See the C<timeout> constructor
363argument. 429argument and method.
364 430
365=cut 431=cut
366 432
367sub on_timeout { 433sub on_timeout {
368 $_[0]{on_timeout} = $_[1]; 434 $_[0]{on_timeout} = $_[1];
369} 435}
370 436
371=item $handle->autocork ($boolean) 437=item $handle->autocork ($boolean)
372 438
373Enables or disables the current autocork behaviour (see C<autocork> 439Enables or disables the current autocork behaviour (see C<autocork>
374constructor argument). 440constructor argument). Changes will only take effect on the next write.
375 441
376=cut 442=cut
443
444sub autocork {
445 $_[0]{autocork} = $_[1];
446}
377 447
378=item $handle->no_delay ($boolean) 448=item $handle->no_delay ($boolean)
379 449
380Enables or disables the C<no_delay> setting (see constructor argument of 450Enables or disables the C<no_delay> setting (see constructor argument of
381the same name for details). 451the same name for details).
387 457
388 eval { 458 eval {
389 local $SIG{__DIE__}; 459 local $SIG{__DIE__};
390 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1]; 460 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1];
391 }; 461 };
462}
463
464=item $handle->on_starttls ($cb)
465
466Replace the current C<on_starttls> callback (see the C<on_starttls> constructor argument).
467
468=cut
469
470sub on_starttls {
471 $_[0]{on_starttls} = $_[1];
472}
473
474=item $handle->on_stoptls ($cb)
475
476Replace the current C<on_stoptls> callback (see the C<on_stoptls> constructor argument).
477
478=cut
479
480sub on_starttls {
481 $_[0]{on_stoptls} = $_[1];
392} 482}
393 483
394############################################################################# 484#############################################################################
395 485
396=item $handle->timeout ($seconds) 486=item $handle->timeout ($seconds)
474 my ($self, $cb) = @_; 564 my ($self, $cb) = @_;
475 565
476 $self->{on_drain} = $cb; 566 $self->{on_drain} = $cb;
477 567
478 $cb->($self) 568 $cb->($self)
479 if $cb && $self->{low_water_mark} >= length $self->{wbuf}; 569 if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
480} 570}
481 571
482=item $handle->push_write ($data) 572=item $handle->push_write ($data)
483 573
484Queues the given scalar to be written. You can push as much data as you 574Queues the given scalar to be written. You can push as much data as you
495 Scalar::Util::weaken $self; 585 Scalar::Util::weaken $self;
496 586
497 my $cb = sub { 587 my $cb = sub {
498 my $len = syswrite $self->{fh}, $self->{wbuf}; 588 my $len = syswrite $self->{fh}, $self->{wbuf};
499 589
500 if ($len >= 0) { 590 if (defined $len) {
501 substr $self->{wbuf}, 0, $len, ""; 591 substr $self->{wbuf}, 0, $len, "";
502 592
503 $self->{_activity} = AnyEvent->now; 593 $self->{_activity} = AnyEvent->now;
504 594
505 $self->{on_drain}($self) 595 $self->{on_drain}($self)
506 if $self->{low_water_mark} >= length $self->{wbuf} 596 if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
507 && $self->{on_drain}; 597 && $self->{on_drain};
508 598
509 delete $self->{_ww} unless length $self->{wbuf}; 599 delete $self->{_ww} unless length $self->{wbuf};
510 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { 600 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
511 $self->_error ($!, 1); 601 $self->_error ($!, 1);
535 625
536 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write") 626 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write")
537 ->($self, @_); 627 ->($self, @_);
538 } 628 }
539 629
540 if ($self->{filter_w}) { 630 if ($self->{tls}) {
541 $self->{filter_w}($self, \$_[0]); 631 $self->{_tls_wbuf} .= $_[0];
632
633 &_dotls ($self);
542 } else { 634 } else {
543 $self->{wbuf} .= $_[0]; 635 $self->{wbuf} .= $_[0];
544 $self->_drain_wbuf; 636 $self->_drain_wbuf;
545 } 637 }
546} 638}
563=cut 655=cut
564 656
565register_write_type netstring => sub { 657register_write_type netstring => sub {
566 my ($self, $string) = @_; 658 my ($self, $string) = @_;
567 659
568 sprintf "%d:%s,", (length $string), $string 660 (length $string) . ":$string,"
569}; 661};
570 662
571=item packstring => $format, $data 663=item packstring => $format, $data
572 664
573An octet string prefixed with an encoded length. The encoding C<$format> 665An octet string prefixed with an encoded length. The encoding C<$format>
638 730
639 pack "w/a*", Storable::nfreeze ($ref) 731 pack "w/a*", Storable::nfreeze ($ref)
640}; 732};
641 733
642=back 734=back
735
736=item $handle->push_shutdown
737
738Sometimes you know you want to close the socket after writing your data
739before it was actually written. One way to do that is to replace your
740C<on_drain> handler by a callback that shuts down the socket (and set
741C<low_water_mark> to C<0>). This method is a shorthand for just that, and
742replaces the C<on_drain> callback with:
743
744 sub { shutdown $_[0]{fh}, 1 } # for push_shutdown
745
746This simply shuts down the write side and signals an EOF condition to the
747the peer.
748
749You can rely on the normal read queue and C<on_eof> handling
750afterwards. This is the cleanest way to close a connection.
751
752=cut
753
754sub push_shutdown {
755 my ($self) = @_;
756
757 delete $self->{low_water_mark};
758 $self->on_drain (sub { shutdown $_[0]{fh}, 1 });
759}
643 760
644=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args) 761=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args)
645 762
646This function (not method) lets you add your own types to C<push_write>. 763This function (not method) lets you add your own types to C<push_write>.
647Whenever the given C<type> is used, C<push_write> will invoke the code 764Whenever the given C<type> is used, C<push_write> will invoke the code
751 ) { 868 ) {
752 $self->_error (&Errno::ENOSPC, 1), return; 869 $self->_error (&Errno::ENOSPC, 1), return;
753 } 870 }
754 871
755 while () { 872 while () {
873 # we need to use a separate tls read buffer, as we must not receive data while
874 # we are draining the buffer, and this can only happen with TLS.
875 $self->{rbuf} .= delete $self->{_tls_rbuf} if exists $self->{_tls_rbuf};
876
756 my $len = length $self->{rbuf}; 877 my $len = length $self->{rbuf};
757 878
758 if (my $cb = shift @{ $self->{_queue} }) { 879 if (my $cb = shift @{ $self->{_queue} }) {
759 unless ($cb->($self)) { 880 unless ($cb->($self)) {
760 if ($self->{_eof}) { 881 if ($self->{_eof}) {
782 903
783 last; # more data might arrive 904 last; # more data might arrive
784 } 905 }
785 } else { 906 } else {
786 # read side becomes idle 907 # read side becomes idle
787 delete $self->{_rw}; 908 delete $self->{_rw} unless $self->{tls};
788 last; 909 last;
789 } 910 }
790 } 911 }
791 912
792 if ($self->{_eof}) { 913 if ($self->{_eof}) {
793 if ($self->{on_eof}) { 914 if ($self->{on_eof}) {
794 $self->{on_eof}($self) 915 $self->{on_eof}($self)
795 } else { 916 } else {
796 $self->_error (0, 1); 917 $self->_error (0, 1, "Unexpected end-of-file");
797 } 918 }
798 } 919 }
799 920
800 # may need to restart read watcher 921 # may need to restart read watcher
801 unless ($self->{_rw}) { 922 unless ($self->{_rw}) {
821 942
822=item $handle->rbuf 943=item $handle->rbuf
823 944
824Returns the read buffer (as a modifiable lvalue). 945Returns the read buffer (as a modifiable lvalue).
825 946
826You can access the read buffer directly as the C<< ->{rbuf} >> member, if 947You can access the read buffer directly as the C<< ->{rbuf} >>
827you want. 948member, if you want. However, the only operation allowed on the
949read buffer (apart from looking at it) is removing data from its
950beginning. Otherwise modifying or appending to it is not allowed and will
951lead to hard-to-track-down bugs.
828 952
829NOTE: The read buffer should only be used or modified if the C<on_read>, 953NOTE: The read buffer should only be used or modified if the C<on_read>,
830C<push_read> or C<unshift_read> methods are used. The other read methods 954C<push_read> or C<unshift_read> methods are used. The other read methods
831automatically manage the read buffer. 955automatically manage the read buffer.
832 956
1087An octet string prefixed with an encoded length. The encoding C<$format> 1211An octet string prefixed with an encoded length. The encoding C<$format>
1088uses the same format as a Perl C<pack> format, but must specify a single 1212uses the same format as a Perl C<pack> format, but must specify a single
1089integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an 1213integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an
1090optional C<!>, C<< < >> or C<< > >> modifier). 1214optional C<!>, C<< < >> or C<< > >> modifier).
1091 1215
1092DNS over TCP uses a prefix of C<n>, EPP uses a prefix of C<N>. 1216For example, DNS over TCP uses a prefix of C<n> (2 octet network order),
1217EPP uses a prefix of C<N> (4 octtes).
1093 1218
1094Example: read a block of data prefixed by its length in BER-encoded 1219Example: read a block of data prefixed by its length in BER-encoded
1095format (very efficient). 1220format (very efficient).
1096 1221
1097 $handle->push_read (packstring => "w", sub { 1222 $handle->push_read (packstring => "w", sub {
1127 } 1252 }
1128}; 1253};
1129 1254
1130=item json => $cb->($handle, $hash_or_arrayref) 1255=item json => $cb->($handle, $hash_or_arrayref)
1131 1256
1132Reads a JSON object or array, decodes it and passes it to the callback. 1257Reads a JSON object or array, decodes it and passes it to the
1258callback. When a parse error occurs, an C<EBADMSG> error will be raised.
1133 1259
1134If a C<json> object was passed to the constructor, then that will be used 1260If a C<json> object was passed to the constructor, then that will be used
1135for the final decode, otherwise it will create a JSON coder expecting UTF-8. 1261for the final decode, otherwise it will create a JSON coder expecting UTF-8.
1136 1262
1137This read type uses the incremental parser available with JSON version 1263This read type uses the incremental parser available with JSON version
1146=cut 1272=cut
1147 1273
1148register_read_type json => sub { 1274register_read_type json => sub {
1149 my ($self, $cb) = @_; 1275 my ($self, $cb) = @_;
1150 1276
1151 require JSON; 1277 my $json = $self->{json} ||=
1278 eval { require JSON::XS; JSON::XS->new->utf8 }
1279 || do { require JSON; JSON->new->utf8 };
1152 1280
1153 my $data; 1281 my $data;
1154 my $rbuf = \$self->{rbuf}; 1282 my $rbuf = \$self->{rbuf};
1155 1283
1156 my $json = $self->{json} ||= JSON->new->utf8;
1157
1158 sub { 1284 sub {
1159 my $ref = $json->incr_parse ($self->{rbuf}); 1285 my $ref = eval { $json->incr_parse ($self->{rbuf}) };
1160 1286
1161 if ($ref) { 1287 if ($ref) {
1162 $self->{rbuf} = $json->incr_text; 1288 $self->{rbuf} = $json->incr_text;
1163 $json->incr_text = ""; 1289 $json->incr_text = "";
1164 $cb->($self, $ref); 1290 $cb->($self, $ref);
1165 1291
1166 1 1292 1
1293 } elsif ($@) {
1294 # error case
1295 $json->incr_skip;
1296
1297 $self->{rbuf} = $json->incr_text;
1298 $json->incr_text = "";
1299
1300 $self->_error (&Errno::EBADMSG);
1301
1302 ()
1167 } else { 1303 } else {
1168 $self->{rbuf} = ""; 1304 $self->{rbuf} = "";
1305
1169 () 1306 ()
1170 } 1307 }
1171 } 1308 }
1172}; 1309};
1173 1310
1250Note that AnyEvent::Handle will automatically C<start_read> for you when 1387Note that AnyEvent::Handle will automatically C<start_read> for you when
1251you change the C<on_read> callback or push/unshift a read callback, and it 1388you change the C<on_read> callback or push/unshift a read callback, and it
1252will automatically C<stop_read> for you when neither C<on_read> is set nor 1389will automatically C<stop_read> for you when neither C<on_read> is set nor
1253there are any read requests in the queue. 1390there are any read requests in the queue.
1254 1391
1392These methods will have no effect when in TLS mode (as TLS doesn't support
1393half-duplex connections).
1394
1255=cut 1395=cut
1256 1396
1257sub stop_read { 1397sub stop_read {
1258 my ($self) = @_; 1398 my ($self) = @_;
1259 1399
1260 delete $self->{_rw}; 1400 delete $self->{_rw} unless $self->{tls};
1261} 1401}
1262 1402
1263sub start_read { 1403sub start_read {
1264 my ($self) = @_; 1404 my ($self) = @_;
1265 1405
1266 unless ($self->{_rw} || $self->{_eof}) { 1406 unless ($self->{_rw} || $self->{_eof}) {
1267 Scalar::Util::weaken $self; 1407 Scalar::Util::weaken $self;
1268 1408
1269 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { 1409 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub {
1270 my $rbuf = $self->{filter_r} ? \my $buf : \$self->{rbuf}; 1410 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1271 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; 1411 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf;
1272 1412
1273 if ($len > 0) { 1413 if ($len > 0) {
1274 $self->{_activity} = AnyEvent->now; 1414 $self->{_activity} = AnyEvent->now;
1275 1415
1276 $self->{filter_r} 1416 if ($self->{tls}) {
1277 ? $self->{filter_r}($self, $rbuf) 1417 Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);
1278 : $self->{_in_drain} || $self->_drain_rbuf; 1418
1419 &_dotls ($self);
1420 } else {
1421 $self->_drain_rbuf unless $self->{_in_drain};
1422 }
1279 1423
1280 } elsif (defined $len) { 1424 } elsif (defined $len) {
1281 delete $self->{_rw}; 1425 delete $self->{_rw};
1282 $self->{_eof} = 1; 1426 $self->{_eof} = 1;
1283 $self->_drain_rbuf unless $self->{_in_drain}; 1427 $self->_drain_rbuf unless $self->{_in_drain};
1287 } 1431 }
1288 }); 1432 });
1289 } 1433 }
1290} 1434}
1291 1435
1436our $ERROR_SYSCALL;
1437our $ERROR_WANT_READ;
1438
1439sub _tls_error {
1440 my ($self, $err) = @_;
1441
1442 return $self->_error ($!, 1)
1443 if $err == Net::SSLeay::ERROR_SYSCALL ();
1444
1445 my $err =Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ());
1446
1447 # reduce error string to look less scary
1448 $err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /;
1449
1450 if ($self->{_on_starttls}) {
1451 (delete $self->{_on_starttls})->($self, undef, $err);
1452 &_freetls;
1453 } else {
1454 &_freetls;
1455 $self->_error (&Errno::EPROTO, 1, $err);
1456 }
1457}
1458
1459# poll the write BIO and send the data if applicable
1460# also decode read data if possible
1461# this is basiclaly our TLS state machine
1462# more efficient implementations are possible with openssl,
1463# but not with the buggy and incomplete Net::SSLeay.
1292sub _dotls { 1464sub _dotls {
1293 my ($self) = @_; 1465 my ($self) = @_;
1294 1466
1295 my $buf; 1467 my $tmp;
1296 1468
1297 if (length $self->{_tls_wbuf}) { 1469 if (length $self->{_tls_wbuf}) {
1298 while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { 1470 while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {
1299 substr $self->{_tls_wbuf}, 0, $len, ""; 1471 substr $self->{_tls_wbuf}, 0, $tmp, "";
1300 } 1472 }
1301 }
1302 1473
1474 $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);
1475 return $self->_tls_error ($tmp)
1476 if $tmp != $ERROR_WANT_READ
1477 && ($tmp != $ERROR_SYSCALL || $!);
1478 }
1479
1480 while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
1481 unless (length $tmp) {
1482 $self->{_on_starttls}
1483 and (delete $self->{_on_starttls})->($self, undef, "EOF during handshake"); # ???
1484 &_freetls;
1485
1486 if ($self->{on_stoptls}) {
1487 $self->{on_stoptls}($self);
1488 return;
1489 } else {
1490 # let's treat SSL-eof as we treat normal EOF
1491 delete $self->{_rw};
1492 $self->{_eof} = 1;
1493 }
1494 }
1495
1496 $self->{_tls_rbuf} .= $tmp;
1497 $self->_drain_rbuf unless $self->{_in_drain};
1498 $self->{tls} or return; # tls session might have gone away in callback
1499 }
1500
1501 $tmp = Net::SSLeay::get_error ($self->{tls}, -1);
1502 return $self->_tls_error ($tmp)
1503 if $tmp != $ERROR_WANT_READ
1504 && ($tmp != $ERROR_SYSCALL || $!);
1505
1303 if (length ($buf = Net::SSLeay::BIO_read ($self->{_wbio}))) { 1506 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
1304 $self->{wbuf} .= $buf; 1507 $self->{wbuf} .= $tmp;
1305 $self->_drain_wbuf; 1508 $self->_drain_wbuf;
1306 } 1509 }
1307 1510
1308 while (defined ($buf = Net::SSLeay::read ($self->{tls}))) { 1511 $self->{_on_starttls}
1309 if (length $buf) { 1512 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
1310 $self->{rbuf} .= $buf; 1513 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
1311 $self->_drain_rbuf unless $self->{_in_drain};
1312 } else {
1313 # let's treat SSL-eof as we treat normal EOF
1314 $self->{_eof} = 1;
1315 $self->_shutdown;
1316 return;
1317 }
1318 }
1319
1320 my $err = Net::SSLeay::get_error ($self->{tls}, -1);
1321
1322 if ($err!= Net::SSLeay::ERROR_WANT_READ ()) {
1323 if ($err == Net::SSLeay::ERROR_SYSCALL ()) {
1324 return $self->_error ($!, 1);
1325 } elsif ($err == Net::SSLeay::ERROR_SSL ()) {
1326 return $self->_error (&Errno::EIO, 1);
1327 }
1328
1329 # all others are fine for our purposes
1330 }
1331} 1514}
1332 1515
1333=item $handle->starttls ($tls[, $tls_ctx]) 1516=item $handle->starttls ($tls[, $tls_ctx])
1334 1517
1335Instead of starting TLS negotiation immediately when the AnyEvent::Handle 1518Instead of starting TLS negotiation immediately when the AnyEvent::Handle
1337C<starttls>. 1520C<starttls>.
1338 1521
1339The first argument is the same as the C<tls> constructor argument (either 1522The first argument is the same as the C<tls> constructor argument (either
1340C<"connect">, C<"accept"> or an existing Net::SSLeay object). 1523C<"connect">, C<"accept"> or an existing Net::SSLeay object).
1341 1524
1342The second argument is the optional C<Net::SSLeay::CTX> object that is 1525The second argument is the optional C<AnyEvent::TLS> object that is used
1343used when AnyEvent::Handle has to create its own TLS connection object. 1526when AnyEvent::Handle has to create its own TLS connection object, or
1527a hash reference with C<< key => value >> pairs that will be used to
1528construct a new context.
1344 1529
1345The TLS connection object will end up in C<< $handle->{tls} >> after this 1530The TLS connection object will end up in C<< $handle->{tls} >>, the TLS
1346call and can be used or changed to your liking. Note that the handshake 1531context in C<< $handle->{tls_ctx} >> after this call and can be used or
1347might have already started when this function returns. 1532changed to your liking. Note that the handshake might have already started
1533when this function returns.
1348 1534
1535If it an error to start a TLS handshake more than once per
1536AnyEvent::Handle object (this is due to bugs in OpenSSL).
1537
1349=cut 1538=cut
1539
1540our %TLS_CACHE; #TODO not yet documented, should we?
1350 1541
1351sub starttls { 1542sub starttls {
1352 my ($self, $ssl, $ctx) = @_; 1543 my ($self, $ssl, $ctx) = @_;
1353 1544
1354 $self->stoptls; 1545 require Net::SSLeay;
1355 1546
1356 if ($ssl eq "accept") { 1547 Carp::croak "it is an error to call starttls more than once on an AnyEvent::Handle object"
1357 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1548 if $self->{tls};
1358 Net::SSLeay::set_accept_state ($ssl); 1549
1359 } elsif ($ssl eq "connect") { 1550 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
1360 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1551 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
1361 Net::SSLeay::set_connect_state ($ssl); 1552
1553 $ctx ||= $self->{tls_ctx};
1554
1555 if ("HASH" eq ref $ctx) {
1556 require AnyEvent::TLS;
1557
1558 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context
1559
1560 if ($ctx->{cache}) {
1561 my $key = $ctx+0;
1562 $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx;
1563 } else {
1564 $ctx = new AnyEvent::TLS %$ctx;
1565 }
1566 }
1362 } 1567
1363 1568 $self->{tls_ctx} = $ctx || TLS_CTX ();
1364 $self->{tls} = $ssl; 1569 $self->{tls} = $ssl = $self->{tls_ctx}->_get_session ($ssl, $self, $self->{peername});
1365 1570
1366 # basically, this is deep magic (because SSL_read should have the same issues) 1571 # basically, this is deep magic (because SSL_read should have the same issues)
1367 # but the openssl maintainers basically said: "trust us, it just works". 1572 # but the openssl maintainers basically said: "trust us, it just works".
1368 # (unfortunately, we have to hardcode constants because the abysmally misdesigned 1573 # (unfortunately, we have to hardcode constants because the abysmally misdesigned
1369 # and mismaintained ssleay-module doesn't even offer them). 1574 # and mismaintained ssleay-module doesn't even offer them).
1370 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html 1575 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html
1576 #
1577 # in short: this is a mess.
1578 #
1579 # note that we do not try to keep the length constant between writes as we are required to do.
1580 # we assume that most (but not all) of this insanity only applies to non-blocking cases,
1581 # and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to
1582 # have identity issues in that area.
1371 Net::SSLeay::CTX_set_mode ($self->{tls}, 1583# Net::SSLeay::CTX_set_mode ($ssl,
1372 (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) 1584# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
1373 | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); 1585# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
1586 Net::SSLeay::CTX_set_mode ($ssl, 1|2);
1374 1587
1375 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1588 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1376 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1589 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1377 1590
1378 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio}); 1591 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio});
1379 1592
1380 $self->{filter_w} = sub { 1593 $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }
1381 $_[0]{_tls_wbuf} .= ${$_[1]}; 1594 if $self->{on_starttls};
1382 &_dotls; 1595
1383 }; 1596 &_dotls; # need to trigger the initial handshake
1384 $self->{filter_r} = sub { 1597 $self->start_read; # make sure we actually do read
1385 Net::SSLeay::BIO_write ($_[0]{_rbio}, ${$_[1]});
1386 &_dotls;
1387 };
1388} 1598}
1389 1599
1390=item $handle->stoptls 1600=item $handle->stoptls
1391 1601
1392Destroys the SSL connection, if any. Partial read or write data will be 1602Shuts down the SSL connection - this makes a proper EOF handshake by
1393lost. 1603sending a close notify to the other side, but since OpenSSL doesn't
1604support non-blocking shut downs, it is not possible to re-use the stream
1605afterwards.
1394 1606
1395=cut 1607=cut
1396 1608
1397sub stoptls { 1609sub stoptls {
1398 my ($self) = @_; 1610 my ($self) = @_;
1399 1611
1400 Net::SSLeay::free (delete $self->{tls}) if $self->{tls}; 1612 if ($self->{tls}) {
1613 Net::SSLeay::shutdown ($self->{tls});
1401 1614
1402 delete $self->{_rbio}; 1615 &_dotls;
1403 delete $self->{_wbio}; 1616
1404 delete $self->{_tls_wbuf}; 1617# # we don't give a shit. no, we do, but we can't. no...#d#
1405 delete $self->{filter_r}; 1618# # we, we... have to use openssl :/#d#
1406 delete $self->{filter_w}; 1619# &_freetls;#d#
1620 }
1621}
1622
1623sub _freetls {
1624 my ($self) = @_;
1625
1626 return unless $self->{tls};
1627
1628 $self->{tls_ctx}->_put_session (delete $self->{tls});
1629
1630 delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)};
1407} 1631}
1408 1632
1409sub DESTROY { 1633sub DESTROY {
1410 my $self = shift; 1634 my ($self) = @_;
1411 1635
1412 $self->stoptls; 1636 &_freetls;
1413 1637
1414 my $linger = exists $self->{linger} ? $self->{linger} : 3600; 1638 my $linger = exists $self->{linger} ? $self->{linger} : 3600;
1415 1639
1416 if ($linger && length $self->{wbuf}) { 1640 if ($linger && length $self->{wbuf}) {
1417 my $fh = delete $self->{fh}; 1641 my $fh = delete $self->{fh};
1432 @linger = (); 1656 @linger = ();
1433 }); 1657 });
1434 } 1658 }
1435} 1659}
1436 1660
1661=item $handle->destroy
1662
1663Shuts down the handle object as much as possible - this call ensures that
1664no further callbacks will be invoked and as many resources as possible
1665will be freed. You must not call any methods on the object afterwards.
1666
1667Normally, you can just "forget" any references to an AnyEvent::Handle
1668object and it will simply shut down. This works in fatal error and EOF
1669callbacks, as well as code outside. It does I<NOT> work in a read or write
1670callback, so when you want to destroy the AnyEvent::Handle object from
1671within such an callback. You I<MUST> call C<< ->destroy >> explicitly in
1672that case.
1673
1674Destroying the handle object in this way has the advantage that callbacks
1675will be removed as well, so if those are the only reference holders (as
1676is common), then one doesn't need to do anything special to break any
1677reference cycles.
1678
1679The handle might still linger in the background and write out remaining
1680data, as specified by the C<linger> option, however.
1681
1682=cut
1683
1684sub destroy {
1685 my ($self) = @_;
1686
1687 $self->DESTROY;
1688 %$self = ();
1689}
1690
1437=item AnyEvent::Handle::TLS_CTX 1691=item AnyEvent::Handle::TLS_CTX
1438 1692
1439This function creates and returns the Net::SSLeay::CTX object used by 1693This function creates and returns the AnyEvent::TLS object used by default
1440default for TLS mode. 1694for TLS mode.
1441 1695
1442The context is created like this: 1696The context is created by calling L<AnyEvent::TLS> without any arguments.
1443
1444 Net::SSLeay::load_error_strings;
1445 Net::SSLeay::SSLeay_add_ssl_algorithms;
1446 Net::SSLeay::randomize;
1447
1448 my $CTX = Net::SSLeay::CTX_new;
1449
1450 Net::SSLeay::CTX_set_options $CTX, Net::SSLeay::OP_ALL
1451 1697
1452=cut 1698=cut
1453 1699
1454our $TLS_CTX; 1700our $TLS_CTX;
1455 1701
1456sub TLS_CTX() { 1702sub TLS_CTX() {
1457 $TLS_CTX || do { 1703 $TLS_CTX ||= do {
1458 require Net::SSLeay; 1704 require AnyEvent::TLS;
1459 1705
1460 Net::SSLeay::load_error_strings (); 1706 new AnyEvent::TLS
1461 Net::SSLeay::SSLeay_add_ssl_algorithms ();
1462 Net::SSLeay::randomize ();
1463
1464 $TLS_CTX = Net::SSLeay::CTX_new ();
1465
1466 Net::SSLeay::CTX_set_options ($TLS_CTX, Net::SSLeay::OP_ALL ());
1467
1468 $TLS_CTX
1469 } 1707 }
1470} 1708}
1471 1709
1472=back 1710=back
1711
1712
1713=head1 NONFREQUENTLY ASKED QUESTIONS
1714
1715=over 4
1716
1717=item I C<undef> the AnyEvent::Handle reference inside my callback and
1718still get further invocations!
1719
1720That's because AnyEvent::Handle keeps a reference to itself when handling
1721read or write callbacks.
1722
1723It is only safe to "forget" the reference inside EOF or error callbacks,
1724from within all other callbacks, you need to explicitly call the C<<
1725->destroy >> method.
1726
1727=item I get different callback invocations in TLS mode/Why can't I pause
1728reading?
1729
1730Unlike, say, TCP, TLS connections do not consist of two independent
1731communication channels, one for each direction. Or put differently. The
1732read and write directions are not independent of each other: you cannot
1733write data unless you are also prepared to read, and vice versa.
1734
1735This can mean than, in TLS mode, you might get C<on_error> or C<on_eof>
1736callback invocations when you are not expecting any read data - the reason
1737is that AnyEvent::Handle always reads in TLS mode.
1738
1739During the connection, you have to make sure that you always have a
1740non-empty read-queue, or an C<on_read> watcher. At the end of the
1741connection (or when you no longer want to use it) you can call the
1742C<destroy> method.
1743
1744=item How do I read data until the other side closes the connection?
1745
1746If you just want to read your data into a perl scalar, the easiest way
1747to achieve this is by setting an C<on_read> callback that does nothing,
1748clearing the C<on_eof> callback and in the C<on_error> callback, the data
1749will be in C<$_[0]{rbuf}>:
1750
1751 $handle->on_read (sub { });
1752 $handle->on_eof (undef);
1753 $handle->on_error (sub {
1754 my $data = delete $_[0]{rbuf};
1755 });
1756
1757The reason to use C<on_error> is that TCP connections, due to latencies
1758and packets loss, might get closed quite violently with an error, when in
1759fact, all data has been received.
1760
1761It is usually better to use acknowledgements when transferring data,
1762to make sure the other side hasn't just died and you got the data
1763intact. This is also one reason why so many internet protocols have an
1764explicit QUIT command.
1765
1766=item I don't want to destroy the handle too early - how do I wait until
1767all data has been written?
1768
1769After writing your last bits of data, set the C<on_drain> callback
1770and destroy the handle in there - with the default setting of
1771C<low_water_mark> this will be called precisely when all data has been
1772written to the socket:
1773
1774 $handle->push_write (...);
1775 $handle->on_drain (sub {
1776 warn "all data submitted to the kernel\n";
1777 undef $handle;
1778 });
1779
1780If you just want to queue some data and then signal EOF to the other side,
1781consider using C<< ->push_shutdown >> instead.
1782
1783=item I want to contact a TLS/SSL server, I don't care about security.
1784
1785If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS,
1786simply connect to it and then create the AnyEvent::Handle with the C<tls>
1787parameter:
1788
1789 tcp_connect $host, $port, sub {
1790 my ($fh) = @_;
1791
1792 my $handle = new AnyEvent::Handle
1793 fh => $fh,
1794 tls => "connect",
1795 on_error => sub { ... };
1796
1797 $handle->push_write (...);
1798 };
1799
1800=item I want to contact a TLS/SSL server, I do care about security.
1801
1802Then you should additionally enable certificate verification, including
1803peername verification, if the protocol you use supports it (see
1804L<AnyEvent::TLS>, C<verify_peername>).
1805
1806E.g. for HTTPS:
1807
1808 tcp_connect $host, $port, sub {
1809 my ($fh) = @_;
1810
1811 my $handle = new AnyEvent::Handle
1812 fh => $fh,
1813 peername => $host,
1814 tls => "connect",
1815 tls_ctx => { verify => 1, verify_peername => "https" },
1816 ...
1817
1818Note that you must specify the hostname you connected to (or whatever
1819"peername" the protocol needs) as the C<peername> argument, otherwise no
1820peername verification will be done.
1821
1822The above will use the system-dependent default set of trusted CA
1823certificates. If you want to check against a specific CA, add the
1824C<ca_file> (or C<ca_cert>) arguments to C<tls_ctx>:
1825
1826 tls_ctx => {
1827 verify => 1,
1828 verify_peername => "https",
1829 ca_file => "my-ca-cert.pem",
1830 },
1831
1832=item I want to create a TLS/SSL server, how do I do that?
1833
1834Well, you first need to get a server certificate and key. You have
1835three options: a) ask a CA (buy one, use cacert.org etc.) b) create a
1836self-signed certificate (cheap. check the search engine of your choice,
1837there are many tutorials on the net) or c) make your own CA (tinyca2 is a
1838nice program for that purpose).
1839
1840Then create a file with your private key (in PEM format, see
1841L<AnyEvent::TLS>), followed by the certificate (also in PEM format). The
1842file should then look like this:
1843
1844 -----BEGIN RSA PRIVATE KEY-----
1845 ...header data
1846 ... lots of base64'y-stuff
1847 -----END RSA PRIVATE KEY-----
1848
1849 -----BEGIN CERTIFICATE-----
1850 ... lots of base64'y-stuff
1851 -----END CERTIFICATE-----
1852
1853The important bits are the "PRIVATE KEY" and "CERTIFICATE" parts. Then
1854specify this file as C<cert_file>:
1855
1856 tcp_server undef, $port, sub {
1857 my ($fh) = @_;
1858
1859 my $handle = new AnyEvent::Handle
1860 fh => $fh,
1861 tls => "accept",
1862 tls_ctx => { cert_file => "my-server-keycert.pem" },
1863 ...
1864
1865When you have intermediate CA certificates that your clients might not
1866know about, just append them to the C<cert_file>.
1867
1868=back
1869
1473 1870
1474=head1 SUBCLASSING AnyEvent::Handle 1871=head1 SUBCLASSING AnyEvent::Handle
1475 1872
1476In many cases, you might want to subclass AnyEvent::Handle. 1873In many cases, you might want to subclass AnyEvent::Handle.
1477 1874

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines