… | |
… | |
14 | |
14 | |
15 | AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent |
15 | AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent |
16 | |
16 | |
17 | =cut |
17 | =cut |
18 | |
18 | |
19 | our $VERSION = 4.232; |
19 | our $VERSION = 4.3; |
20 | |
20 | |
21 | =head1 SYNOPSIS |
21 | =head1 SYNOPSIS |
22 | |
22 | |
23 | use AnyEvent; |
23 | use AnyEvent; |
24 | use AnyEvent::Handle; |
24 | use AnyEvent::Handle; |
… | |
… | |
49 | |
49 | |
50 | This module is a helper module to make it easier to do event-based I/O on |
50 | This module is a helper module to make it easier to do event-based I/O on |
51 | filehandles. For utility functions for doing non-blocking connects and accepts |
51 | filehandles. For utility functions for doing non-blocking connects and accepts |
52 | on sockets see L<AnyEvent::Util>. |
52 | on sockets see L<AnyEvent::Util>. |
53 | |
53 | |
|
|
54 | The L<AnyEvent::Intro> tutorial contains some well-documented |
|
|
55 | AnyEvent::Handle examples. |
|
|
56 | |
54 | In the following, when the documentation refers to of "bytes" then this |
57 | In the following, when the documentation refers to of "bytes" then this |
55 | means characters. As sysread and syswrite are used for all I/O, their |
58 | means characters. As sysread and syswrite are used for all I/O, their |
56 | treatment of characters applies to this module as well. |
59 | treatment of characters applies to this module as well. |
57 | |
60 | |
58 | All callbacks will be invoked with the handle object as their first |
61 | All callbacks will be invoked with the handle object as their first |
59 | argument. |
62 | argument. |
|
|
63 | |
|
|
64 | =head2 SIGPIPE is not handled by this module |
|
|
65 | |
|
|
66 | SIGPIPE is not handled by this module, so one of the practical |
|
|
67 | requirements of using it is to ignore SIGPIPE (C<$SIG{PIPE} = |
|
|
68 | 'IGNORE'>). At least, this is highly recommend in a networked program: If |
|
|
69 | you use AnyEvent::Handle in a filter program (like sort), exiting on |
|
|
70 | SIGPIPE is probably the right thing to do. |
60 | |
71 | |
61 | =head1 METHODS |
72 | =head1 METHODS |
62 | |
73 | |
63 | =over 4 |
74 | =over 4 |
64 | |
75 | |
… | |
… | |
100 | occured, such as not being able to resolve the hostname, failure to |
111 | occured, such as not being able to resolve the hostname, failure to |
101 | connect or a read error. |
112 | connect or a read error. |
102 | |
113 | |
103 | Some errors are fatal (which is indicated by C<$fatal> being true). On |
114 | Some errors are fatal (which is indicated by C<$fatal> being true). On |
104 | fatal errors the handle object will be shut down and will not be usable |
115 | fatal errors the handle object will be shut down and will not be usable |
105 | (but you are free to look at the current C< ->rbuf >). Examples of fatal |
116 | (but you are free to look at the current C<< ->rbuf >>). Examples of fatal |
106 | errors are an EOF condition with active (but unsatisifable) read watchers |
117 | errors are an EOF condition with active (but unsatisifable) read watchers |
107 | (C<EPIPE>) or I/O errors. |
118 | (C<EPIPE>) or I/O errors. |
108 | |
119 | |
109 | Non-fatal errors can be retried by simply returning, but it is recommended |
120 | Non-fatal errors can be retried by simply returning, but it is recommended |
110 | to simply ignore this parameter and instead abondon the handle object |
121 | to simply ignore this parameter and instead abondon the handle object |
… | |
… | |
149 | =item timeout => $fractional_seconds |
160 | =item timeout => $fractional_seconds |
150 | |
161 | |
151 | If non-zero, then this enables an "inactivity" timeout: whenever this many |
162 | If non-zero, then this enables an "inactivity" timeout: whenever this many |
152 | seconds pass without a successful read or write on the underlying file |
163 | seconds pass without a successful read or write on the underlying file |
153 | handle, the C<on_timeout> callback will be invoked (and if that one is |
164 | handle, the C<on_timeout> callback will be invoked (and if that one is |
154 | missing, an C<ETIMEDOUT> error will be raised). |
165 | missing, a non-fatal C<ETIMEDOUT> error will be raised). |
155 | |
166 | |
156 | Note that timeout processing is also active when you currently do not have |
167 | Note that timeout processing is also active when you currently do not have |
157 | any outstanding read or write requests: If you plan to keep the connection |
168 | any outstanding read or write requests: If you plan to keep the connection |
158 | idle then you should disable the timout temporarily or ignore the timeout |
169 | idle then you should disable the timout temporarily or ignore the timeout |
159 | in the C<on_timeout> callback. |
170 | in the C<on_timeout> callback, in which case AnyEvent::Handle will simply |
|
|
171 | restart the timeout. |
160 | |
172 | |
161 | Zero (the default) disables this timeout. |
173 | Zero (the default) disables this timeout. |
162 | |
174 | |
163 | =item on_timeout => $cb->($handle) |
175 | =item on_timeout => $cb->($handle) |
164 | |
176 | |
… | |
… | |
168 | |
180 | |
169 | =item rbuf_max => <bytes> |
181 | =item rbuf_max => <bytes> |
170 | |
182 | |
171 | If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>) |
183 | If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>) |
172 | when the read buffer ever (strictly) exceeds this size. This is useful to |
184 | when the read buffer ever (strictly) exceeds this size. This is useful to |
173 | avoid denial-of-service attacks. |
185 | avoid some forms of denial-of-service attacks. |
174 | |
186 | |
175 | For example, a server accepting connections from untrusted sources should |
187 | For example, a server accepting connections from untrusted sources should |
176 | be configured to accept only so-and-so much data that it cannot act on |
188 | be configured to accept only so-and-so much data that it cannot act on |
177 | (for example, when expecting a line, an attacker could send an unlimited |
189 | (for example, when expecting a line, an attacker could send an unlimited |
178 | amount of data without a callback ever being called as long as the line |
190 | amount of data without a callback ever being called as long as the line |
179 | isn't finished). |
191 | isn't finished). |
180 | |
192 | |
181 | =item autocork => <boolean> |
193 | =item autocork => <boolean> |
182 | |
194 | |
183 | When disabled (the default), then C<push_write> will try to immediately |
195 | When disabled (the default), then C<push_write> will try to immediately |
184 | write the data to the handle if possible. This avoids having to register |
196 | write the data to the handle, if possible. This avoids having to register |
185 | a write watcher and wait for the next event loop iteration, but can be |
197 | a write watcher and wait for the next event loop iteration, but can |
186 | inefficient if you write multiple small chunks (this disadvantage is |
198 | be inefficient if you write multiple small chunks (on the wire, this |
187 | usually avoided by your kernel's nagle algorithm, see C<low_delay>). |
199 | disadvantage is usually avoided by your kernel's nagle algorithm, see |
|
|
200 | C<no_delay>, but this option can save costly syscalls). |
188 | |
201 | |
189 | When enabled, then writes will always be queued till the next event loop |
202 | When enabled, then writes will always be queued till the next event loop |
190 | iteration. This is efficient when you do many small writes per iteration, |
203 | iteration. This is efficient when you do many small writes per iteration, |
191 | but less efficient when you do a single write only. |
204 | but less efficient when you do a single write only per iteration (or when |
|
|
205 | the write buffer often is full). It also increases write latency. |
192 | |
206 | |
193 | =item no_delay => <boolean> |
207 | =item no_delay => <boolean> |
194 | |
208 | |
195 | When doing small writes on sockets, your operating system kernel might |
209 | When doing small writes on sockets, your operating system kernel might |
196 | wait a bit for more data before actually sending it out. This is called |
210 | wait a bit for more data before actually sending it out. This is called |
197 | the Nagle algorithm, and usually it is beneficial. |
211 | the Nagle algorithm, and usually it is beneficial. |
198 | |
212 | |
199 | In some situations you want as low a delay as possible, which cna be |
213 | In some situations you want as low a delay as possible, which can be |
200 | accomplishd by setting this option to true. |
214 | accomplishd by setting this option to a true value. |
201 | |
215 | |
202 | The default is your opertaing system's default behaviour, this option |
216 | The default is your opertaing system's default behaviour (most likely |
203 | explicitly enables or disables it, if possible. |
217 | enabled), this option explicitly enables or disables it, if possible. |
204 | |
218 | |
205 | =item read_size => <bytes> |
219 | =item read_size => <bytes> |
206 | |
220 | |
207 | The default read block size (the amount of bytes this module will try to read |
221 | The default read block size (the amount of bytes this module will |
208 | during each (loop iteration). Default: C<8192>. |
222 | try to read during each loop iteration, which affects memory |
|
|
223 | requirements). Default: C<8192>. |
209 | |
224 | |
210 | =item low_water_mark => <bytes> |
225 | =item low_water_mark => <bytes> |
211 | |
226 | |
212 | Sets the amount of bytes (default: C<0>) that make up an "empty" write |
227 | Sets the amount of bytes (default: C<0>) that make up an "empty" write |
213 | buffer: If the write reaches this size or gets even samller it is |
228 | buffer: If the write reaches this size or gets even samller it is |
214 | considered empty. |
229 | considered empty. |
215 | |
230 | |
|
|
231 | Sometimes it can be beneficial (for performance reasons) to add data to |
|
|
232 | the write buffer before it is fully drained, but this is a rare case, as |
|
|
233 | the operating system kernel usually buffers data as well, so the default |
|
|
234 | is good in almost all cases. |
|
|
235 | |
216 | =item linger => <seconds> |
236 | =item linger => <seconds> |
217 | |
237 | |
218 | If non-zero (default: C<3600>), then the destructor of the |
238 | If non-zero (default: C<3600>), then the destructor of the |
219 | AnyEvent::Handle object will check wether there is still outstanding write |
239 | AnyEvent::Handle object will check whether there is still outstanding |
220 | data and will install a watcher that will write out this data. No errors |
240 | write data and will install a watcher that will write this data to the |
221 | will be reported (this mostly matches how the operating system treats |
241 | socket. No errors will be reported (this mostly matches how the operating |
222 | outstanding data at socket close time). |
242 | system treats outstanding data at socket close time). |
223 | |
243 | |
224 | This will not work for partial TLS data that could not yet been |
244 | This will not work for partial TLS data that could not be encoded |
225 | encoded. This data will be lost. |
245 | yet. This data will be lost. Calling the C<stoptls> method in time might |
|
|
246 | help. |
226 | |
247 | |
227 | =item tls => "accept" | "connect" | Net::SSLeay::SSL object |
248 | =item tls => "accept" | "connect" | Net::SSLeay::SSL object |
228 | |
249 | |
229 | When this parameter is given, it enables TLS (SSL) mode, that means it |
250 | When this parameter is given, it enables TLS (SSL) mode, that means |
230 | will start making tls handshake and will transparently encrypt/decrypt |
251 | AnyEvent will start a TLS handshake as soon as the conenction has been |
231 | data. |
252 | established and will transparently encrypt/decrypt data afterwards. |
232 | |
253 | |
233 | TLS mode requires Net::SSLeay to be installed (it will be loaded |
254 | TLS mode requires Net::SSLeay to be installed (it will be loaded |
234 | automatically when you try to create a TLS handle). |
255 | automatically when you try to create a TLS handle): this module doesn't |
|
|
256 | have a dependency on that module, so if your module requires it, you have |
|
|
257 | to add the dependency yourself. |
235 | |
258 | |
236 | For the TLS server side, use C<accept>, and for the TLS client side of a |
259 | Unlike TCP, TLS has a server and client side: for the TLS server side, use |
237 | connection, use C<connect> mode. |
260 | C<accept>, and for the TLS client side of a connection, use C<connect> |
|
|
261 | mode. |
238 | |
262 | |
239 | You can also provide your own TLS connection object, but you have |
263 | You can also provide your own TLS connection object, but you have |
240 | to make sure that you call either C<Net::SSLeay::set_connect_state> |
264 | to make sure that you call either C<Net::SSLeay::set_connect_state> |
241 | or C<Net::SSLeay::set_accept_state> on it before you pass it to |
265 | or C<Net::SSLeay::set_accept_state> on it before you pass it to |
242 | AnyEvent::Handle. |
266 | AnyEvent::Handle. |
243 | |
267 | |
244 | See the C<starttls> method if you need to start TLS negotiation later. |
268 | See the C<< ->starttls >> method for when need to start TLS negotiation later. |
245 | |
269 | |
246 | =item tls_ctx => $ssl_ctx |
270 | =item tls_ctx => $ssl_ctx |
247 | |
271 | |
248 | Use the given Net::SSLeay::CTX object to create the new TLS connection |
272 | Use the given C<Net::SSLeay::CTX> object to create the new TLS connection |
249 | (unless a connection object was specified directly). If this parameter is |
273 | (unless a connection object was specified directly). If this parameter is |
250 | missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. |
274 | missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. |
251 | |
275 | |
252 | =item json => JSON or JSON::XS object |
276 | =item json => JSON or JSON::XS object |
253 | |
277 | |
254 | This is the json coder object used by the C<json> read and write types. |
278 | This is the json coder object used by the C<json> read and write types. |
255 | |
279 | |
256 | If you don't supply it, then AnyEvent::Handle will create and use a |
280 | If you don't supply it, then AnyEvent::Handle will create and use a |
257 | suitable one, which will write and expect UTF-8 encoded JSON texts. |
281 | suitable one (on demand), which will write and expect UTF-8 encoded JSON |
|
|
282 | texts. |
258 | |
283 | |
259 | Note that you are responsible to depend on the JSON module if you want to |
284 | Note that you are responsible to depend on the JSON module if you want to |
260 | use this functionality, as AnyEvent does not have a dependency itself. |
285 | use this functionality, as AnyEvent does not have a dependency itself. |
261 | |
286 | |
262 | =item filter_r => $cb |
|
|
263 | |
|
|
264 | =item filter_w => $cb |
|
|
265 | |
|
|
266 | These exist, but are undocumented at this time. |
|
|
267 | |
|
|
268 | =back |
287 | =back |
269 | |
288 | |
270 | =cut |
289 | =cut |
271 | |
290 | |
272 | sub new { |
291 | sub new { |
… | |
… | |
276 | |
295 | |
277 | $self->{fh} or Carp::croak "mandatory argument fh is missing"; |
296 | $self->{fh} or Carp::croak "mandatory argument fh is missing"; |
278 | |
297 | |
279 | AnyEvent::Util::fh_nonblocking $self->{fh}, 1; |
298 | AnyEvent::Util::fh_nonblocking $self->{fh}, 1; |
280 | |
299 | |
281 | if ($self->{tls}) { |
|
|
282 | require Net::SSLeay; |
|
|
283 | $self->starttls (delete $self->{tls}, delete $self->{tls_ctx}); |
300 | $self->starttls (delete $self->{tls}, delete $self->{tls_ctx}) |
284 | } |
301 | if $self->{tls}; |
285 | |
302 | |
286 | $self->{_activity} = AnyEvent->now; |
303 | $self->{_activity} = AnyEvent->now; |
287 | $self->_timeout; |
304 | $self->_timeout; |
288 | |
305 | |
289 | $self->on_drain (delete $self->{on_drain}) if exists $self->{on_drain}; |
306 | $self->on_drain (delete $self->{on_drain}) if exists $self->{on_drain}; |
… | |
… | |
301 | delete $self->{_tw}; |
318 | delete $self->{_tw}; |
302 | delete $self->{_rw}; |
319 | delete $self->{_rw}; |
303 | delete $self->{_ww}; |
320 | delete $self->{_ww}; |
304 | delete $self->{fh}; |
321 | delete $self->{fh}; |
305 | |
322 | |
306 | $self->stoptls; |
323 | &_freetls; |
307 | |
324 | |
308 | delete $self->{on_read}; |
325 | delete $self->{on_read}; |
309 | delete $self->{_queue}; |
326 | delete $self->{_queue}; |
310 | } |
327 | } |
311 | |
328 | |
… | |
… | |
324 | } |
341 | } |
325 | } |
342 | } |
326 | |
343 | |
327 | =item $fh = $handle->fh |
344 | =item $fh = $handle->fh |
328 | |
345 | |
329 | This method returns the file handle of the L<AnyEvent::Handle> object. |
346 | This method returns the file handle used to create the L<AnyEvent::Handle> object. |
330 | |
347 | |
331 | =cut |
348 | =cut |
332 | |
349 | |
333 | sub fh { $_[0]{fh} } |
350 | sub fh { $_[0]{fh} } |
334 | |
351 | |
… | |
… | |
352 | $_[0]{on_eof} = $_[1]; |
369 | $_[0]{on_eof} = $_[1]; |
353 | } |
370 | } |
354 | |
371 | |
355 | =item $handle->on_timeout ($cb) |
372 | =item $handle->on_timeout ($cb) |
356 | |
373 | |
357 | Replace the current C<on_timeout> callback, or disables the callback |
374 | Replace the current C<on_timeout> callback, or disables the callback (but |
358 | (but not the timeout) if C<$cb> = C<undef>. See C<timeout> constructor |
375 | not the timeout) if C<$cb> = C<undef>. See the C<timeout> constructor |
359 | argument. |
376 | argument and method. |
360 | |
377 | |
361 | =cut |
378 | =cut |
362 | |
379 | |
363 | sub on_timeout { |
380 | sub on_timeout { |
364 | $_[0]{on_timeout} = $_[1]; |
381 | $_[0]{on_timeout} = $_[1]; |
… | |
… | |
470 | my ($self, $cb) = @_; |
487 | my ($self, $cb) = @_; |
471 | |
488 | |
472 | $self->{on_drain} = $cb; |
489 | $self->{on_drain} = $cb; |
473 | |
490 | |
474 | $cb->($self) |
491 | $cb->($self) |
475 | if $cb && $self->{low_water_mark} >= length $self->{wbuf}; |
492 | if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf}); |
476 | } |
493 | } |
477 | |
494 | |
478 | =item $handle->push_write ($data) |
495 | =item $handle->push_write ($data) |
479 | |
496 | |
480 | Queues the given scalar to be written. You can push as much data as you |
497 | Queues the given scalar to be written. You can push as much data as you |
… | |
… | |
497 | substr $self->{wbuf}, 0, $len, ""; |
514 | substr $self->{wbuf}, 0, $len, ""; |
498 | |
515 | |
499 | $self->{_activity} = AnyEvent->now; |
516 | $self->{_activity} = AnyEvent->now; |
500 | |
517 | |
501 | $self->{on_drain}($self) |
518 | $self->{on_drain}($self) |
502 | if $self->{low_water_mark} >= length $self->{wbuf} |
519 | if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf}) |
503 | && $self->{on_drain}; |
520 | && $self->{on_drain}; |
504 | |
521 | |
505 | delete $self->{_ww} unless length $self->{wbuf}; |
522 | delete $self->{_ww} unless length $self->{wbuf}; |
506 | } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { |
523 | } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { |
507 | $self->_error ($!, 1); |
524 | $self->_error ($!, 1); |
… | |
… | |
531 | |
548 | |
532 | @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write") |
549 | @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write") |
533 | ->($self, @_); |
550 | ->($self, @_); |
534 | } |
551 | } |
535 | |
552 | |
536 | if ($self->{filter_w}) { |
553 | if ($self->{tls}) { |
537 | $self->{filter_w}($self, \$_[0]); |
554 | $self->{_tls_wbuf} .= $_[0]; |
|
|
555 | &_dotls ($self); |
538 | } else { |
556 | } else { |
539 | $self->{wbuf} .= $_[0]; |
557 | $self->{wbuf} .= $_[0]; |
540 | $self->_drain_wbuf; |
558 | $self->_drain_wbuf; |
541 | } |
559 | } |
542 | } |
560 | } |
… | |
… | |
778 | |
796 | |
779 | last; # more data might arrive |
797 | last; # more data might arrive |
780 | } |
798 | } |
781 | } else { |
799 | } else { |
782 | # read side becomes idle |
800 | # read side becomes idle |
783 | delete $self->{_rw}; |
801 | delete $self->{_rw} unless $self->{tls}; |
784 | last; |
802 | last; |
785 | } |
803 | } |
786 | } |
804 | } |
787 | |
805 | |
788 | if ($self->{_eof}) { |
806 | if ($self->{_eof}) { |
… | |
… | |
1246 | Note that AnyEvent::Handle will automatically C<start_read> for you when |
1264 | Note that AnyEvent::Handle will automatically C<start_read> for you when |
1247 | you change the C<on_read> callback or push/unshift a read callback, and it |
1265 | you change the C<on_read> callback or push/unshift a read callback, and it |
1248 | will automatically C<stop_read> for you when neither C<on_read> is set nor |
1266 | will automatically C<stop_read> for you when neither C<on_read> is set nor |
1249 | there are any read requests in the queue. |
1267 | there are any read requests in the queue. |
1250 | |
1268 | |
|
|
1269 | These methods will have no effect when in TLS mode (as TLS doesn't support |
|
|
1270 | half-duplex connections). |
|
|
1271 | |
1251 | =cut |
1272 | =cut |
1252 | |
1273 | |
1253 | sub stop_read { |
1274 | sub stop_read { |
1254 | my ($self) = @_; |
1275 | my ($self) = @_; |
1255 | |
1276 | |
1256 | delete $self->{_rw}; |
1277 | delete $self->{_rw} unless $self->{tls}; |
1257 | } |
1278 | } |
1258 | |
1279 | |
1259 | sub start_read { |
1280 | sub start_read { |
1260 | my ($self) = @_; |
1281 | my ($self) = @_; |
1261 | |
1282 | |
1262 | unless ($self->{_rw} || $self->{_eof}) { |
1283 | unless ($self->{_rw} || $self->{_eof}) { |
1263 | Scalar::Util::weaken $self; |
1284 | Scalar::Util::weaken $self; |
1264 | |
1285 | |
1265 | $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { |
1286 | $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { |
1266 | my $rbuf = $self->{filter_r} ? \my $buf : \$self->{rbuf}; |
1287 | my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf}); |
1267 | my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; |
1288 | my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; |
1268 | |
1289 | |
1269 | if ($len > 0) { |
1290 | if ($len > 0) { |
1270 | $self->{_activity} = AnyEvent->now; |
1291 | $self->{_activity} = AnyEvent->now; |
1271 | |
1292 | |
1272 | $self->{filter_r} |
1293 | if ($self->{tls}) { |
1273 | ? $self->{filter_r}($self, $rbuf) |
1294 | Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf); |
1274 | : $self->{_in_drain} || $self->_drain_rbuf; |
1295 | &_dotls ($self); |
|
|
1296 | } else { |
|
|
1297 | $self->_drain_rbuf unless $self->{_in_drain}; |
|
|
1298 | } |
1275 | |
1299 | |
1276 | } elsif (defined $len) { |
1300 | } elsif (defined $len) { |
1277 | delete $self->{_rw}; |
1301 | delete $self->{_rw}; |
1278 | $self->{_eof} = 1; |
1302 | $self->{_eof} = 1; |
1279 | $self->_drain_rbuf unless $self->{_in_drain}; |
1303 | $self->_drain_rbuf unless $self->{_in_drain}; |
… | |
… | |
1294 | while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { |
1318 | while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { |
1295 | substr $self->{_tls_wbuf}, 0, $len, ""; |
1319 | substr $self->{_tls_wbuf}, 0, $len, ""; |
1296 | } |
1320 | } |
1297 | } |
1321 | } |
1298 | |
1322 | |
1299 | if (length ($buf = Net::SSLeay::BIO_read ($self->{_wbio}))) { |
|
|
1300 | $self->{wbuf} .= $buf; |
|
|
1301 | $self->_drain_wbuf; |
|
|
1302 | } |
|
|
1303 | |
|
|
1304 | while (defined ($buf = Net::SSLeay::read ($self->{tls}))) { |
1323 | while (defined ($buf = Net::SSLeay::read ($self->{tls}))) { |
1305 | if (length $buf) { |
1324 | unless (length $buf) { |
1306 | $self->{rbuf} .= $buf; |
|
|
1307 | $self->_drain_rbuf unless $self->{_in_drain}; |
|
|
1308 | } else { |
|
|
1309 | # let's treat SSL-eof as we treat normal EOF |
1325 | # let's treat SSL-eof as we treat normal EOF |
|
|
1326 | delete $self->{_rw}; |
1310 | $self->{_eof} = 1; |
1327 | $self->{_eof} = 1; |
1311 | $self->_shutdown; |
1328 | &_freetls; |
1312 | return; |
|
|
1313 | } |
1329 | } |
|
|
1330 | |
|
|
1331 | $self->{rbuf} .= $buf; |
|
|
1332 | $self->_drain_rbuf unless $self->{_in_drain}; |
|
|
1333 | $self->{tls} or return; # tls session might have gone away in callback |
1314 | } |
1334 | } |
1315 | |
1335 | |
1316 | my $err = Net::SSLeay::get_error ($self->{tls}, -1); |
1336 | my $err = Net::SSLeay::get_error ($self->{tls}, -1); |
1317 | |
1337 | |
1318 | if ($err!= Net::SSLeay::ERROR_WANT_READ ()) { |
1338 | if ($err!= Net::SSLeay::ERROR_WANT_READ ()) { |
… | |
… | |
1322 | return $self->_error (&Errno::EIO, 1); |
1342 | return $self->_error (&Errno::EIO, 1); |
1323 | } |
1343 | } |
1324 | |
1344 | |
1325 | # all others are fine for our purposes |
1345 | # all others are fine for our purposes |
1326 | } |
1346 | } |
|
|
1347 | |
|
|
1348 | if (length ($buf = Net::SSLeay::BIO_read ($self->{_wbio}))) { |
|
|
1349 | $self->{wbuf} .= $buf; |
|
|
1350 | $self->_drain_wbuf; |
|
|
1351 | } |
1327 | } |
1352 | } |
1328 | |
1353 | |
1329 | =item $handle->starttls ($tls[, $tls_ctx]) |
1354 | =item $handle->starttls ($tls[, $tls_ctx]) |
1330 | |
1355 | |
1331 | Instead of starting TLS negotiation immediately when the AnyEvent::Handle |
1356 | Instead of starting TLS negotiation immediately when the AnyEvent::Handle |
… | |
… | |
1340 | |
1365 | |
1341 | The TLS connection object will end up in C<< $handle->{tls} >> after this |
1366 | The TLS connection object will end up in C<< $handle->{tls} >> after this |
1342 | call and can be used or changed to your liking. Note that the handshake |
1367 | call and can be used or changed to your liking. Note that the handshake |
1343 | might have already started when this function returns. |
1368 | might have already started when this function returns. |
1344 | |
1369 | |
|
|
1370 | If it an error to start a TLS handshake more than once per |
|
|
1371 | AnyEvent::Handle object (this is due to bugs in OpenSSL). |
|
|
1372 | |
1345 | =cut |
1373 | =cut |
1346 | |
1374 | |
1347 | sub starttls { |
1375 | sub starttls { |
1348 | my ($self, $ssl, $ctx) = @_; |
1376 | my ($self, $ssl, $ctx) = @_; |
1349 | |
1377 | |
1350 | $self->stoptls; |
1378 | require Net::SSLeay; |
1351 | |
1379 | |
|
|
1380 | Carp::croak "it is an error to call starttls more than once on an Anyevent::Handle object" |
|
|
1381 | if $self->{tls}; |
|
|
1382 | |
1352 | if ($ssl eq "accept") { |
1383 | if ($ssl eq "accept") { |
1353 | $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); |
1384 | $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); |
1354 | Net::SSLeay::set_accept_state ($ssl); |
1385 | Net::SSLeay::set_accept_state ($ssl); |
1355 | } elsif ($ssl eq "connect") { |
1386 | } elsif ($ssl eq "connect") { |
1356 | $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); |
1387 | $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); |
… | |
… | |
1362 | # basically, this is deep magic (because SSL_read should have the same issues) |
1393 | # basically, this is deep magic (because SSL_read should have the same issues) |
1363 | # but the openssl maintainers basically said: "trust us, it just works". |
1394 | # but the openssl maintainers basically said: "trust us, it just works". |
1364 | # (unfortunately, we have to hardcode constants because the abysmally misdesigned |
1395 | # (unfortunately, we have to hardcode constants because the abysmally misdesigned |
1365 | # and mismaintained ssleay-module doesn't even offer them). |
1396 | # and mismaintained ssleay-module doesn't even offer them). |
1366 | # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html |
1397 | # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html |
|
|
1398 | # |
|
|
1399 | # in short: this is a mess. |
|
|
1400 | # |
|
|
1401 | # note that we do not try to keep the length constant between writes as we are required to do. |
|
|
1402 | # we assume that most (but not all) of this insanity only applies to non-blocking cases, |
|
|
1403 | # and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to |
|
|
1404 | # have identity issues in that area. |
1367 | Net::SSLeay::CTX_set_mode ($self->{tls}, |
1405 | Net::SSLeay::CTX_set_mode ($self->{tls}, |
1368 | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) |
1406 | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) |
1369 | | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); |
1407 | | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); |
1370 | |
1408 | |
1371 | $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); |
1409 | $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); |
1372 | $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); |
1410 | $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); |
1373 | |
1411 | |
1374 | Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio}); |
1412 | Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio}); |
1375 | |
1413 | |
1376 | $self->{filter_w} = sub { |
1414 | &_dotls; # need to trigger the initial handshake |
1377 | $_[0]{_tls_wbuf} .= ${$_[1]}; |
1415 | $self->start_read; # make sure we actually do read |
1378 | &_dotls; |
|
|
1379 | }; |
|
|
1380 | $self->{filter_r} = sub { |
|
|
1381 | Net::SSLeay::BIO_write ($_[0]{_rbio}, ${$_[1]}); |
|
|
1382 | &_dotls; |
|
|
1383 | }; |
|
|
1384 | } |
1416 | } |
1385 | |
1417 | |
1386 | =item $handle->stoptls |
1418 | =item $handle->stoptls |
1387 | |
1419 | |
1388 | Destroys the SSL connection, if any. Partial read or write data will be |
1420 | Shuts down the SSL connection - this makes a proper EOF handshake by |
1389 | lost. |
1421 | sending a close notify to the other side, but since OpenSSL doesn't |
|
|
1422 | support non-blocking shut downs, it is not possible to re-use the stream |
|
|
1423 | afterwards. |
1390 | |
1424 | |
1391 | =cut |
1425 | =cut |
1392 | |
1426 | |
1393 | sub stoptls { |
1427 | sub stoptls { |
1394 | my ($self) = @_; |
1428 | my ($self) = @_; |
1395 | |
1429 | |
|
|
1430 | if ($self->{tls}) { |
|
|
1431 | Net::SSLeay::shutdown ($self->{tls}); |
|
|
1432 | |
|
|
1433 | &_dotls; |
|
|
1434 | |
|
|
1435 | # we don't give a shit. no, we do, but we can't. no... |
|
|
1436 | # we, we... have to use openssl :/ |
|
|
1437 | &_freetls; |
|
|
1438 | } |
|
|
1439 | } |
|
|
1440 | |
|
|
1441 | sub _freetls { |
|
|
1442 | my ($self) = @_; |
|
|
1443 | |
|
|
1444 | return unless $self->{tls}; |
|
|
1445 | |
1396 | Net::SSLeay::free (delete $self->{tls}) if $self->{tls}; |
1446 | Net::SSLeay::free (delete $self->{tls}); |
1397 | |
1447 | |
1398 | delete $self->{_rbio}; |
1448 | delete @$self{qw(_rbio _wbio _tls_wbuf)}; |
1399 | delete $self->{_wbio}; |
|
|
1400 | delete $self->{_tls_wbuf}; |
|
|
1401 | delete $self->{filter_r}; |
|
|
1402 | delete $self->{filter_w}; |
|
|
1403 | } |
1449 | } |
1404 | |
1450 | |
1405 | sub DESTROY { |
1451 | sub DESTROY { |
1406 | my $self = shift; |
1452 | my $self = shift; |
1407 | |
1453 | |
1408 | $self->stoptls; |
1454 | &_freetls; |
1409 | |
1455 | |
1410 | my $linger = exists $self->{linger} ? $self->{linger} : 3600; |
1456 | my $linger = exists $self->{linger} ? $self->{linger} : 3600; |
1411 | |
1457 | |
1412 | if ($linger && length $self->{wbuf}) { |
1458 | if ($linger && length $self->{wbuf}) { |
1413 | my $fh = delete $self->{fh}; |
1459 | my $fh = delete $self->{fh}; |
… | |
… | |
1465 | } |
1511 | } |
1466 | } |
1512 | } |
1467 | |
1513 | |
1468 | =back |
1514 | =back |
1469 | |
1515 | |
|
|
1516 | |
|
|
1517 | =head1 NONFREQUENTLY ASKED QUESTIONS |
|
|
1518 | |
|
|
1519 | =over 4 |
|
|
1520 | |
|
|
1521 | =item How do I read data until the other side closes the connection? |
|
|
1522 | |
|
|
1523 | If you just want to read your data into a perl scalar, the easiest way to achieve this is |
|
|
1524 | by setting an C<on_read> callback that does nothing, clearing the C<on_eof> callback |
|
|
1525 | and in the C<on_error> callback, the data will be in C<$_[0]{rbuf}>: |
|
|
1526 | |
|
|
1527 | $handle->on_read (sub { }); |
|
|
1528 | $handle->on_eof (undef); |
|
|
1529 | $handle->on_error (sub { |
|
|
1530 | my $data = delete $_[0]{rbuf}; |
|
|
1531 | undef $handle; |
|
|
1532 | }); |
|
|
1533 | |
|
|
1534 | The reason to use C<on_error> is that TCP connections, due to latencies |
|
|
1535 | and packets loss, might get closed quite violently with an error, when in |
|
|
1536 | fact, all data has been received. |
|
|
1537 | |
|
|
1538 | It is usually better to use acknowledgements when transfering data, |
|
|
1539 | to make sure the other side hasn't just died and you got the data |
|
|
1540 | intact. This is also one reason why so many internet protocols have an |
|
|
1541 | explicit QUIT command. |
|
|
1542 | |
|
|
1543 | |
|
|
1544 | =item I don't want to destroy the handle too early - how do I wait until all data has been sent? |
|
|
1545 | |
|
|
1546 | After writing your last bits of data, set the C<on_drain> callback |
|
|
1547 | and destroy the handle in there - with the default setting of |
|
|
1548 | C<low_water_mark> this will be called precisely when all data has been |
|
|
1549 | written to the socket: |
|
|
1550 | |
|
|
1551 | $handle->push_write (...); |
|
|
1552 | $handle->on_drain (sub { |
|
|
1553 | warn "all data submitted to the kernel\n"; |
|
|
1554 | undef $handle; |
|
|
1555 | }); |
|
|
1556 | |
|
|
1557 | =back |
|
|
1558 | |
|
|
1559 | |
1470 | =head1 SUBCLASSING AnyEvent::Handle |
1560 | =head1 SUBCLASSING AnyEvent::Handle |
1471 | |
1561 | |
1472 | In many cases, you might want to subclass AnyEvent::Handle. |
1562 | In many cases, you might want to subclass AnyEvent::Handle. |
1473 | |
1563 | |
1474 | To make this easier, a given version of AnyEvent::Handle uses these |
1564 | To make this easier, a given version of AnyEvent::Handle uses these |