=head1 NAME
-perlfaq9 - Networking ($Revision: 1.7 $, $Date: 2002/01/28 04:17:27 $)
+perlfaq9 - Networking ($Revision: 1.9 $, $Date: 2002/04/07 18:46:13 $)
=head1 DESCRIPTION
to Perl, and has its own FAQs and tutorials, and usenet group,
comp.infosystems.www.authoring.cgi
-The original CGI specification is at: http://hoohoo.ncsa.uiuc.edu/cgi/
+The original CGI specification is at: http://hoohoo.ncsa.uiuc.edu/cgi/
-Current best-practice RFC draft at: http://CGI-Spec.Golux.Com/
+Current best-practice RFC draft at: http://CGI-Spec.Golux.Com/
Other relevant documentation listed in: http://www.perl.org/CGI_MetaFAQ.html
The best source of detailed information on URI encoding is RFC 2396.
Basically, the following substitutions do it:
- s/([^\w()'*~!.-])/sprintf '%%%02x', $1/eg; # encode
+ s/([^\w()'*~!.-])/sprintf '%%%02x', ord $1/eg; # encode
s/%([A-Fa-f\d]{2})/chr hex $1/eg; # decode
C</^[\w.-]+\@(?:[\w-]+\.)+\w+$/>. It's a very bad idea. However,
this also throws out many valid ones, and says nothing about
potential deliverability, so it is not suggested. Instead, see
-http://www.cpan.org/authors/Tom_Christiansen/scripts/ckaddr.gz,
+http://www.cpan.org/authors/Tom_Christiansen/scripts/ckaddr.gz ,
which actually checks against the full RFC spec (except for nested
comments), looks for addresses you may not wish to accept mail to
(say, Bill Clinton or your postmaster), and then makes sure that the