.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" Set up some character translations and predefined strings. \*(-- will .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left .\" double quote, and \*(R" will give a right double quote. \*(C+ will .\" give a nicer C++. Capital omega is used to do unbreakable dashes and .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, .\" nothing in troff, for use with C<>. .tr \(*W- .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' .ie n \{\ . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} .el\{\ . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{ . if \nF \{ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. . \" fudge factors for nroff and troff .if n \{\ . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] \fP .\} .if t \{\ . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff .if n \{\ . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} .if t \{\ . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' .ds 8 \h'\*(#H'\(*b\h'-\*(#H' .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] .ds ae a\h'-(\w'a'u*4/10)'e .ds Ae A\h'-(\w'A'u*4/10)'E . \" corrections for vroff .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' . \" for low resolution devices (crt and lpr) .if \n(.H>23 .if \n(.V>19 \ \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} .rm #[ #] #H #V #F C .\" ======================================================================== .\" .IX Title "POE::Component::SSLify 3pm" .TH POE::Component::SSLify 3pm "2014-11-14" "perl v5.20.2" "User Contributed Perl Documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH "NAME" POE::Component::SSLify \- Makes using SSL in the world of POE easy! .SH "VERSION" .IX Header "VERSION" .Vb 1 \& This document describes v1.012 of POE::Component::SSLify \- released November 14, 2014 as part of POE\-Component\-SSLify. .Ve .SH "SYNOPSIS" .IX Header "SYNOPSIS" .Vb 1 \& # look at the DESCRIPTION for client and server example code .Ve .SH "DESCRIPTION" .IX Header "DESCRIPTION" This component is a method to simplify the SSLification of a socket before it is passed to a POE::Wheel::ReadWrite wheel in your application. .SS "Client usage" .IX Subsection "Client usage" .Vb 2 \& # Import the module \& use POE::Component::SSLify qw( Client_SSLify ); \& \& # Create a normal SocketFactory wheel and connect to a SSL\-enabled server \& my $factory = POE::Wheel::SocketFactory\->new; \& \& # Time passes, SocketFactory gives you a socket when it connects in SuccessEvent \& # Convert the socket into a SSL socket POE can communicate with \& my $socket = shift; \& eval { $socket = Client_SSLify( $socket ) }; \& if ( $@ ) { \& # Unable to SSLify it... \& } \& \& # Now, hand it off to ReadWrite \& my $rw = POE::Wheel::ReadWrite\->new( \& Handle => $socket, \& # other options as usual \& ); .Ve .SS "Server usage" .IX Subsection "Server usage" .Vb 2 \& # !!! Make sure you have a public key + certificate \& # excellent howto: http://www.akadia.com/services/ssh_test_certificate.html \& \& # Import the module \& use POE::Component::SSLify qw( Server_SSLify SSLify_Options ); \& \& # Set the key + certificate file \& eval { SSLify_Options( \*(Aqserver.key\*(Aq, \*(Aqserver.crt\*(Aq ) }; \& if ( $@ ) { \& # Unable to load key or certificate file... \& } \& \& # Create a normal SocketFactory wheel to listen for connections \& my $factory = POE::Wheel::SocketFactory\->new; \& \& # Time passes, SocketFactory gives you a socket when it gets a connection in SuccessEvent \& # Convert the socket into a SSL socket POE can communicate with \& my $socket = shift; \& eval { $socket = Server_SSLify( $socket ) }; \& if ( $@ ) { \& # Unable to SSLify it... \& } \& \& # Now, hand it off to ReadWrite \& my $rw = POE::Wheel::ReadWrite\->new( \& Handle => $socket, \& # other options as usual \& ); .Ve .SH "FUNCTIONS" .IX Header "FUNCTIONS" .SS "Client_SSLify" .IX Subsection "Client_SSLify" This function sslifies a client-side socket. You can pass several options to it: .PP .Vb 7 \& my $socket = shift; \& $socket = Client_SSLify( $socket, $version, $options, $ctx, $callback ); \& $socket is the non\-ssl socket you got from somewhere ( required ) \& $version is the SSL version you want to use \& $options is the SSL options you want to use \& $ctx is the custom SSL context you want to use \& $callback is the callback hook on success/failure of sslification \& \& # This is an example of the callback and you should pass it as Client_SSLify( $socket, ... , \e&callback ); \& sub callback { \& my( $socket, $status, $errval ) = @_; \& # $socket is the original sslified socket in case you need to play with it \& # $status is either 1 or 0; with 1 signifying success and 0 failure \& # $errval will be defined if $status == 0; it\*(Aqs the numeric SSL error code \& # check http://www.openssl.org/docs/ssl/SSL_get_error.html for the possible error values ( and import them from Net::SSLeay! ) \& \& # The return value from the callback is discarded \& } .Ve .PP If \f(CW$ctx\fR is defined, SSLify will ignore \f(CW$version\fR and \f(CW$options\fR. Otherwise, it will be created from the \f(CW$version\fR and \&\f(CW$options\fR parameters. If all of them are undefined, it will follow the defaults in \*(L"SSLify_ContextCreate\*(R". .PP \&\s-1BEWARE:\s0 If you passed in a \s-1CTX,\s0 SSLify will do Net::SSLeay::CTX_free( \f(CW$ctx\fR ) when the socket is destroyed. This means you cannot reuse contexts! .PP \&\s-1NOTE:\s0 The way to have a client socket with proper certificates set up is: .PP .Vb 3 \& my $socket = shift; # get the socket from somewhere \& my $ctx = SSLify_ContextCreate( \*(Aqserver.key\*(Aq, \*(Aqserver.crt\*(Aq ); \& $socket = Client_SSLify( $socket, undef, undef, $ctx ); .Ve .PP \&\s-1NOTE:\s0 You can pass the callback anywhere in the arguments, we'll figure it out for you! If you want to call a \s-1POE\s0 event, please look into the postback/callback stuff in POE::Session. .PP .Vb 10 \& # we got this from POE::Wheel::SocketFactory \& sub event_SuccessEvent { \& my $socket = $_[ARG0]; \& $socket = Client_SSLify( $socket, $_[SESSION]\->callback( \*(Aqsslify_result\*(Aq ) ); \& $_[HEAP]\->{client} = POE::Wheel::ReadWrite\->new( \& Handle => $socket, \& ... \& ); \& return; \& } \& \& # the callback event \& sub event_sslify_result { \& my ($creation_args, $called_args) = @_[ARG0, ARG1]; \& my( $socket, $status, $errval ) = @$called_args; \& \& if ( $status ) { \& print "Yay, SSLification worked!"; \& } else { \& print "Aw, SSLification failed with error $errval"; \& } \& } .Ve .SS "Server_SSLify" .IX Subsection "Server_SSLify" This function sslifies a server-side socket. You can pass several options to it: .PP .Vb 5 \& my $socket = shift; \& $socket = Server_SSLify( $socket, $ctx, $callback ); \& $socket is the non\-ssl socket you got from somewhere ( required ) \& $ctx is the custom SSL context you want to use; overrides the global ctx set in SSLify_Options \& $callback is the callback hook on success/failure of sslification .Ve .PP \&\s-1BEWARE: \s0\*(L"SSLify_Options\*(R" must be called first if you aren't passing a \f(CW$ctx\fR. If you want to set some options per-connection, do this: .PP .Vb 4 \& my $socket = shift; # get the socket from somewhere \& my $ctx = SSLify_ContextCreate(); \& # set various options on $ctx as desired \& $socket = Server_SSLify( $socket, $ctx ); .Ve .PP \&\s-1NOTE:\s0 You can use \*(L"SSLify_GetCTX\*(R" to modify the global, and avoid doing this on every connection if the options are the same... .PP Please look at \*(L"Client_SSLify\*(R" for more details on the callback hook. .SS "SSLify_ContextCreate" .IX Subsection "SSLify_ContextCreate" Accepts some options, and returns a brand-new Net::SSLeay context object ( \f(CW$ctx\fR ) .PP .Vb 5 \& my $ctx = SSLify_ContextCreate( $key, $cert, $version, $options ); \& $key is the certificate key file \& $cert is the certificate file \& $version is the SSL version to use \& $options is the SSL options to use .Ve .PP You can then call various Net::SSLeay methods on the context .PP .Vb 1 \& my $mode = Net::SSLeay::CTX_get_mode( $ctx ); .Ve .PP By default we don't use the \s-1SSL\s0 key + certificate files .PP By default we use the version: default. Known versions of the \s-1SSL\s0 connection \- look at for more info. .PP .Vb 5 \& * sslv2 \& * sslv3 \& * tlsv1 \& * sslv23 \& * default ( sslv23 ) .Ve .PP By default we don't set any options \- look at for more info. .SS "SSLify_Options" .IX Subsection "SSLify_Options" Call this function to initialize the global server-side context object. This will be the default context whenever you call \&\*(L"Server_SSLify\*(R" without passing a custom context to it. .PP .Vb 5 \& SSLify_Options( $key, $cert, $version, $options ); \& $key is the certificate key file ( required ) \& $cert is the certificate file ( required ) \& $version is the SSL version to use \& $options is the SSL options to use .Ve .PP By default we use the version: default .PP By default we use the options: Net::SSLeay::OP_ALL .PP Please look at \*(L"SSLify_ContextCreate\*(R" for more info on the available versions/options. .SS "SSLify_GetCTX" .IX Subsection "SSLify_GetCTX" Returns the actual Net::SSLeay context object in case you wanted to play with it :) .PP If passed in a socket, it will return that socket's \f(CW$ctx\fR instead of the global. .PP .Vb 2 \& my $ctx = SSLify_GetCTX(); # get the one set via SSLify_Options \& my $ctx = SSLify_GetCTX( $sslified_sock ); # get the one in the object .Ve .SS "SSLify_GetCipher" .IX Subsection "SSLify_GetCipher" Returns the cipher used by the SSLified socket .PP .Vb 1 \& print "SSL Cipher is: " . SSLify_GetCipher( $sslified_sock ) . "\en"; .Ve .PP \&\s-1NOTE:\s0 Doing this immediately after Client_SSLify or Server_SSLify will result in \*(L"(\s-1NONE\s0)\*(R" because the \s-1SSL\s0 handshake is not done yet. The socket is nonblocking, so you will have to wait a little bit for it to get ready. .PP .Vb 11 \& apoc@blackhole:~/mygit/perl\-poe\-sslify/examples$ perl serverclient.pl \& got connection from: 127.0.0.1 \- commencing Server_SSLify() \& SSLified: 127.0.0.1 cipher type: ((NONE)) \& Connected to server, commencing Client_SSLify() \& SSLified the connection to the server \& Connected to SSL server \& Input: hola \& got input from: 127.0.0.1 cipher type: (AES256\-SHA) input: \*(Aqhola\*(Aq \& Got Reply: hola \& Input: ^C \& stopped at serverclient.pl line 126. .Ve .SS "SSLify_GetSocket" .IX Subsection "SSLify_GetSocket" Returns the actual socket used by the SSLified socket, useful for stuff like \fIgetpeername()\fR/\fIgetsockname()\fR .PP .Vb 1 \& print "Remote IP is: " . inet_ntoa( ( unpack_sockaddr_in( getpeername( SSLify_GetSocket( $sslified_sock ) ) ) )[1] ) . "\en"; .Ve .SS "SSLify_GetSSL" .IX Subsection "SSLify_GetSSL" Returns the actual Net::SSLeay object so you can call methods on it .PP .Vb 1 \& print Net::SSLeay::dump_peer_certificate( SSLify_GetSSL( $sslified_sock ) ); .Ve .SS "SSLify_GetStatus" .IX Subsection "SSLify_GetStatus" Returns the status of the \s-1SSL\s0 negotiation/handshake/connection. See for more info. .PP .Vb 4 \& my $status = SSLify_GetStatus( $socket ); \& \-1 = still in negotiation stage ( or error ) \& 0 = internal SSL error, connection will be dead \& 1 = negotiation successful .Ve .SH "NOTES" .IX Header "NOTES" .SS "Socket methods doesn't work" .IX Subsection "Socket methods doesn't work" The new socket this module gives you actually is tied socket magic, so you cannot do stuff like \&\fIgetpeername()\fR or \fIgetsockname()\fR. The only way to do it is to use \*(L"SSLify_GetSocket\*(R" and then operate on the socket it returns. .SS "Dying everywhere..." .IX Subsection "Dying everywhere..." This module will \fIdie()\fR if Net::SSLeay could not be loaded or it is not the version we want. So, it is recommended that you check for errors and not use \s-1SSL,\s0 like so: .PP .Vb 6 \& eval { use POE::Component::SSLify }; \& if ( $@ ) { \& $sslavailable = 0; \& } else { \& $sslavailable = 1; \& } \& \& # Make socket SSL! \& if ( $sslavailable ) { \& eval { $socket = POE::Component::SSLify::Client_SSLify( $socket ) }; \& if ( $@ ) { \& # Unable to SSLify the socket... \& } \& } .Ve .PP \fI\f(CI$IGNORE_SSL_ERRORS\fI\fR .IX Subsection "$IGNORE_SSL_ERRORS" .PP As of SSLify v1.003 you can override this variable to temporarily ignore some \s-1SSL\s0 errors. This is useful if you are doing crazy things with the underlying Net::SSLeay stuff and don't want to die. However, it won't ignore all errors as some is still considered fatal. Here's an example: .PP .Vb 5 \& { \& local $POE::Component::SSLify::IGNORE_SSL_ERRORS=1; \& my $ctx = SSLify_CreateContext(...); \& #Some more stuff \& } .Ve .SS "OpenSSL functions" .IX Subsection "OpenSSL functions" Theoretically you can do anything that Net::SSLeay exports from the OpenSSL libs on the socket. However, I have not tested every possible function against SSLify, so use them carefully! .PP \fINet::SSLeay::renegotiate\fR .IX Subsection "Net::SSLeay::renegotiate" .PP This function has been tested ( it's in \f(CW\*(C`t/2_renegotiate_client.t\*(C'\fR ) but it doesn't work on FreeBSD! I tracked it down to this security advisory: which explains it in detail. The test will skip this function if it detects that you're on a broken system. However, if you have the updated OpenSSL library that fixes this you can use it. .PP \&\s-1NOTE:\s0 Calling this means the callback function you passed in \*(L"Client_SSLify\*(R" or \*(L"Server_SSLify\*(R" will not fire! If you need this please let me know and we can come up with a way to make it work. .SS "Upgrading a non-ssl socket to \s-1SSL\s0" .IX Subsection "Upgrading a non-ssl socket to SSL" You can have a normal plaintext socket, and convert it to \s-1SSL\s0 anytime. Just keep in mind that the client and the server must agree to sslify at the same time, or they will be waiting on each other forever! See \f(CW\*(C`t/3_upgrade.t\*(C'\fR for an example of how this works. .SS "Downgrading a \s-1SSL\s0 socket to non-ssl" .IX Subsection "Downgrading a SSL socket to non-ssl" As of now this is unsupported. If you need this feature please let us know and we'll work on it together! .SS "MSWin32 is not supported" .IX Subsection "MSWin32 is not supported" This module doesn't work on MSWin32 platforms at all ( \s-1XP,\s0 Vista, 7, etc ) because of some weird underlying fd issues. Since I'm not a windows developer, I'm unable to fix this. However, it seems like Cygwin on MSWin32 works just fine! Please help me fix this if you can, thanks! .SS "\s-1LOAD_SSL_ENGINES\s0" .IX Subsection "LOAD_SSL_ENGINES" OpenSSL supports loading ENGINEs to accelerate the crypto algorithms. SSLify v1.004 automatically loaded the engines, but there was some problems on certain platforms that caused coredumps. A big shout-out to BinGOs and CPANTesters for catching this! It's now disabled in v1.007 and you would need to explicitly enable it. .PP .Vb 2 \& sub POE::Component::SSLify::LOAD_SSL_ENGINES () { 1 } \& use POE::Component::SSLify qw( Client::SSLify ); .Ve .SH "EXPORT" .IX Header "EXPORT" Stuffs all of the functions in \f(CW@EXPORT_OK\fR so you have to request them directly. .SH "SEE ALSO" .IX Header "SEE ALSO" Please see those modules/websites for more information related to this module. .IP "\(bu" 4 \&\s-1POE\s0 .IP "\(bu" 4 Net::SSLeay .SH "SUPPORT" .IX Header "SUPPORT" .SS "Perldoc" .IX Subsection "Perldoc" You can find documentation for this module with the perldoc command. .PP .Vb 1 \& perldoc POE::Component::SSLify .Ve .SS "Websites" .IX Subsection "Websites" The following websites have more information about this module, and may be of help to you. As always, in addition to those websites please use your favorite search engine to discover more resources. .IP "\(bu" 4 MetaCPAN .Sp A modern, open-source \s-1CPAN\s0 search engine, useful to view \s-1POD\s0 in \s-1HTML\s0 format. .Sp .IP "\(bu" 4 Search \s-1CPAN\s0 .Sp The default \s-1CPAN\s0 search engine, useful to view \s-1POD\s0 in \s-1HTML\s0 format. .Sp .IP "\(bu" 4 \&\s-1RT: CPAN\s0's Bug Tracker .Sp The \s-1RT \s0( Request Tracker ) website is the default bug/issue tracking system for \s-1CPAN.\s0 .Sp .IP "\(bu" 4 AnnoCPAN .Sp The AnnoCPAN is a website that allows community annotations of Perl module documentation. .Sp .IP "\(bu" 4 \&\s-1CPAN\s0 Ratings .Sp The \s-1CPAN\s0 Ratings is a website that allows community ratings and reviews of Perl modules. .Sp .IP "\(bu" 4 \&\s-1CPAN\s0 Forum .Sp The \s-1CPAN\s0 Forum is a web forum for discussing Perl modules. .Sp .IP "\(bu" 4 \&\s-1CPANTS\s0 .Sp The \s-1CPANTS\s0 is a website that analyzes the Kwalitee ( code metrics ) of a distribution. .Sp .IP "\(bu" 4 \&\s-1CPAN\s0 Testers .Sp The \s-1CPAN\s0 Testers is a network of smokers who run automated tests on uploaded \s-1CPAN\s0 distributions. .Sp .IP "\(bu" 4 \&\s-1CPAN\s0 Testers Matrix .Sp The \s-1CPAN\s0 Testers Matrix is a website that provides a visual overview of the test results for a distribution on various Perls/platforms. .Sp .IP "\(bu" 4 \&\s-1CPAN\s0 Testers Dependencies .Sp The \s-1CPAN\s0 Testers Dependencies is a website that shows a chart of the test results of all dependencies for a distribution. .Sp .SS "Email" .IX Subsection "Email" You can email the author of this module at \f(CW\*(C`APOCAL at cpan.org\*(C'\fR asking for help with any problems you have. .SS "Internet Relay Chat" .IX Subsection "Internet Relay Chat" You can get live help by using \s-1IRC \s0( Internet Relay Chat ). If you don't know what \s-1IRC\s0 is, please read this excellent guide: . Please be courteous and patient when talking to us, as we might be busy or sleeping! You can join those networks/channels and get help: .IP "\(bu" 4 irc.perl.org .Sp You can connect to the server at 'irc.perl.org' and join this channel: #perl\-help then talk to this person for help: Apocalypse. .IP "\(bu" 4 irc.freenode.net .Sp You can connect to the server at 'irc.freenode.net' and join this channel: #perl then talk to this person for help: Apocal. .IP "\(bu" 4 irc.efnet.org .Sp You can connect to the server at 'irc.efnet.org' and join this channel: #perl then talk to this person for help: Ap0cal. .SS "Bugs / Feature Requests" .IX Subsection "Bugs / Feature Requests" Please report any bugs or feature requests by email to \f(CW\*(C`bug\-poe\-component\-sslify at rt.cpan.org\*(C'\fR, or through the web interface at . You will be automatically notified of any progress on the request by the system. .SS "Source Code" .IX Subsection "Source Code" The code is open to the world, and available for you to hack on. Please feel free to browse it and play with it, or whatever. If you want to contribute patches, please send me a diff or prod me to pull from your repository :) .PP .PP .Vb 1 \& git clone https://github.com/apocalypse/perl\-poe\-sslify.git .Ve .SH "AUTHOR" .IX Header "AUTHOR" Apocalypse .SH "ACKNOWLEDGEMENTS" .IX Header "ACKNOWLEDGEMENTS" .Vb 3 \& Original code is entirely Rocco Caputo ( Creator of POE ) \-> I simply \& packaged up the code into something everyone could use and accepted the burden \& of maintaining it :) \& \& From the PoCo::Client::HTTP code =] \& # This code should probably become a POE::Kernel method, \& # seeing as it\*(Aqs rather baroque and potentially useful in a number \& # of places. .Ve .PP \&\s-1ASCENT\s0 also helped a lot with the nonblocking mode, without his hard work this module would still be stuck in the stone age :) .PP A lot of people helped add various features/functions \- please look at the changelog for more detail. .SH "COPYRIGHT AND LICENSE" .IX Header "COPYRIGHT AND LICENSE" This software is copyright (c) 2014 by Apocalypse. .PP This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. .PP The full text of the license can be found in the \&\fI\s-1LICENSE\s0\fR file included with this distribution. .SH "DISCLAIMER OF WARRANTY" .IX Header "DISCLAIMER OF WARRANTY" \&\s-1THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \*(L"AS IS\*(R" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.\s0 .PP \&\s-1IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM \s0(\s-1INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS\s0), \&\s-1EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\s0