3 perlfaq9 - Networking ($Revision: 1.20 $, $Date: 1998/06/22 18:31:09 $)
7 This section deals with questions related to networking, the internet,
10 =head2 My CGI script runs from the command line but not the browser. (500 Server Error)
12 If you can demonstrate that you've read the following FAQs and that
13 your problem isn't something simple that can be easily answered, you'll
14 probably receive a courteous and useful reply to your question if you
15 post it on comp.infosystems.www.authoring.cgi (if it's something to do
16 with HTTP, HTML, or the CGI protocols). Questions that appear to be Perl
17 questions but are really CGI ones that are posted to comp.lang.perl.misc
18 may not be so well received.
20 The useful FAQs and related documents are:
23 http://www.webthing.com/page.cgi/cgifaq
26 http://www.boutell.com/faq/
29 http://www.w3.org/Security/Faq/
32 http://www.w3.org/pub/WWW/Protocols/HTTP/
35 http://www.w3.org/TR/REC-html40/
36 http://www.w3.org/pub/WWW/MarkUp/
39 http://www.w3.org/CGI/
42 http://www.go2net.com/people/paulp/cgi-security/safe-cgi.txt
44 =head2 How can I get better error messages from a CGI program?
46 Use the CGI::Carp module. It replaces C<warn> and C<die>, plus the
47 normal Carp modules C<carp>, C<croak>, and C<confess> functions with
48 more verbose and safer versions. It still sends them to the normal
52 warn "This is a complaint";
53 die "But this one is serious";
55 The following use of CGI::Carp also redirects errors to a file of your choice,
56 placed in a BEGIN block to catch compile-time warnings as well:
59 use CGI::Carp qw(carpout);
60 open(LOG, ">>/var/local/cgi-logs/mycgi-log")
61 or die "Unable to append to mycgi-log: $!\n";
65 You can even arrange for fatal errors to go back to the client browser,
66 which is nice for your own debugging, but might confuse the end user.
68 use CGI::Carp qw(fatalsToBrowser);
71 Even if the error happens before you get the HTTP header out, the module
72 will try to take care of this to avoid the dreaded server 500 errors.
73 Normal warnings still go out to the server error log (or wherever
74 you've sent them with C<carpout>) with the application name and date
77 =head2 How do I remove HTML from a string?
79 The most correct way (albeit not the fastest) is to use HTML::Parse
80 from CPAN (part of the libwww-perl distribution, which is a must-have
81 module for all web hackers).
83 Many folks attempt a simple-minded regular expression approach, like
84 C<s/E<lt>.*?E<gt>//g>, but that fails in many cases because the tags
85 may continue over line breaks, they may contain quoted angle-brackets,
86 or HTML comment may be present. Plus folks forget to convert
87 entities, like C<<> for example.
89 Here's one "simple-minded" approach, that works for most files:
91 #!/usr/bin/perl -p0777
92 s/<(?:[^>'"]*|(['"]).*?\1)*>//gs
94 If you want a more complete solution, see the 3-stage striphtml
96 http://www.perl.com/CPAN/authors/Tom_Christiansen/scripts/striphtml.gz
99 Here are some tricky cases that you should think about when picking
102 <IMG SRC = "foo.gif" ALT = "A > B">
109 <script>if (a<b && a>c)</script>
113 <![INCLUDE CDATA [ >>>>>>>>>>>> ]]>
115 If HTML comments include other tags, those solutions would also break
118 <!-- This section commented out.
119 <B>You can't see me!</B>
122 =head2 How do I extract URLs?
124 A quick but imperfect approach is
127 # qxurl - tchrist@perl.com
128 print "$2\n" while m{
130 A \s+ HREF \s* = \s* (["']) (.*?) \1
134 This version does not adjust relative URLs, understand alternate
135 bases, deal with HTML comments, deal with HREF and NAME attributes in
136 the same tag, or accept URLs themselves as arguments. It also runs
137 about 100x faster than a more "complete" solution using the LWP suite
138 of modules, such as the
139 http://www.perl.com/CPAN/authors/Tom_Christiansen/scripts/xurl.gz
142 =head2 How do I download a file from the user's machine? How do I open a file on another machine?
144 In the context of an HTML form, you can use what's known as
145 B<multipart/form-data> encoding. The CGI.pm module (available from
146 CPAN) supports this in the start_multipart_form() method, which isn't
147 the same as the startform() method.
149 =head2 How do I make a pop-up menu in HTML?
151 Use the B<E<lt>SELECTE<gt>> and B<E<lt>OPTIONE<gt>> tags. The CGI.pm
152 module (available from CPAN) supports this widget, as well as many
153 others, including some that it cleverly synthesizes on its own.
155 =head2 How do I fetch an HTML file?
157 One approach, if you have the lynx text-based HTML browser installed
158 on your system, is this:
160 $html_code = `lynx -source $url`;
161 $text_data = `lynx -dump $url`;
163 The libwww-perl (LWP) modules from CPAN provide a more powerful way to
164 do this. They work through proxies, and don't require lynx:
168 $content = get($URL);
170 # or print HTML from a URL
172 getprint "http://www.sn.no/libwww-perl/";
174 # or print ASCII from HTML from a URL
177 use HTML::FormatText;
179 $html = get("http://www.perl.com/");
181 or die "Can't fetch HTML from http://www.perl.com/";
182 $ascii = HTML::FormatText->new->format(parse_html($html));
185 =head2 How do I automate an HTML form submission?
187 If you're submitting values using the GET method, create a URL and encode
188 the form using the C<query_form> method:
193 my $url = url('http://www.perl.com/cgi-bin/cpan_mod');
194 $url->query_form(module => 'DB_File', readme => 1);
195 $content = get($url);
197 If you're using the POST method, create your own user agent and encode
198 the content appropriately.
200 use HTTP::Request::Common qw(POST);
203 $ua = LWP::UserAgent->new();
204 my $req = POST 'http://www.perl.com/cgi-bin/cpan_mod',
205 [ module => 'DB_File', readme => 1 ];
206 $content = $ua->request($req)->as_string;
208 =head2 How do I decode or create those %-encodings on the web?
210 Here's an example of decoding:
212 $string = "http://altavista.digital.com/cgi-bin/query?pg=q&what=news&fmt=.&q=%2Bcgi-bin+%2Bperl.exe";
213 $string =~ s/%([a-fA-F0-9]{2})/chr(hex($1))/ge;
215 Encoding is a bit harder, because you can't just blindly change
216 all the non-alphanumunder character (C<\W>) into their hex escapes.
217 It's important that characters with special meaning like C</> and C<?>
218 I<not> be translated. Probably the easiest way to get this right is
219 to avoid reinventing the wheel and just use the URI::Escape module,
220 which is part of the libwww-perl package (LWP) available from CPAN.
222 =head2 How do I redirect to another page?
224 Instead of sending back a C<Content-Type> as the headers of your
225 reply, send back a C<Location:> header. Officially this should be a
226 C<URI:> header, so the CGI.pm module (available from CPAN) sends back
229 Location: http://www.domain.com/newpage
230 URI: http://www.domain.com/newpage
232 Note that relative URLs in these headers can cause strange effects
233 because of "optimizations" that servers do.
235 $url = "http://www.perl.com/CPAN/";
236 print "Location: $url\n\n";
239 To be correct to the spec, each of those C<"\n">
240 should really each be C<"\015\012">, but unless you're
241 stuck on MacOS, you probably won't notice.
243 =head2 How do I put a password on my web pages?
245 That depends. You'll need to read the documentation for your web
246 server, or perhaps check some of the other FAQs referenced above.
248 =head2 How do I edit my .htpasswd and .htgroup files with Perl?
250 The HTTPD::UserAdmin and HTTPD::GroupAdmin modules provide a
251 consistent OO interface to these files, regardless of how they're
252 stored. Databases may be text, dbm, Berkley DB or any database with a
253 DBI compatible driver. HTTPD::UserAdmin supports files used by the
254 `Basic' and `Digest' authentication schemes. Here's an example:
256 use HTTPD::UserAdmin ();
258 ->new(DB => "/foo/.htpasswd")
259 ->add($username => $password);
261 =head2 How do I make sure users can't enter values into a form that cause my CGI script to do bad things?
263 Read the CGI security FAQ, at
264 http://www-genome.wi.mit.edu/WWW/faqs/www-security-faq.html, and the
266 http://www.perl.com/CPAN/doc/FAQs/cgi/perl-cgi-faq.html.
268 In brief: use tainting (see L<perlsec>), which makes sure that data
269 from outside your script (eg, CGI parameters) are never used in
270 C<eval> or C<system> calls. In addition to tainting, never use the
271 single-argument form of system() or exec(). Instead, supply the
272 command and arguments as a list, which prevents shell globbing.
274 =head2 How do I parse a mail header?
276 For a quick-and-dirty solution, try this solution derived
277 from page 222 of the 2nd edition of "Programming Perl":
281 $header =~ s/\n\s+/ /g; # merge continuation lines
282 %head = ( UNIX_FROM_LINE, split /^([-\w]+):\s*/m, $header );
284 That solution doesn't do well if, for example, you're trying to
285 maintain all the Received lines. A more complete approach is to use
286 the Mail::Header module from CPAN (part of the MailTools package).
288 =head2 How do I decode a CGI form?
290 You use a standard module, probably CGI.pm. Under no circumstances
291 should you attempt to do so by hand!
293 You'll see a lot of CGI programs that blindly read from STDIN the number
294 of bytes equal to CONTENT_LENGTH for POSTs, or grab QUERY_STRING for
295 decoding GETs. These programs are very poorly written. They only work
296 sometimes. They typically forget to check the return value of the read()
297 system call, which is a cardinal sin. They don't handle HEAD requests.
298 They don't handle multipart forms used for file uploads. They don't deal
299 with GET/POST combinations where query fields are in more than one place.
300 They don't deal with keywords in the query string.
302 In short, they're bad hacks. Resist them at all costs. Please do not be
303 tempted to reinvent the wheel. Instead, use the CGI.pm or CGI_Lite.pm
304 (available from CPAN), or if you're trapped in the module-free land
305 of perl1 .. perl4, you might look into cgi-lib.pl (available from
306 http://www.bio.cam.ac.uk/web/form.html).
308 Make sure you know whether to use a GET or a POST in your form.
309 GETs should only be used for something that doesn't update the server.
310 Otherwise you can get mangled databases and repeated feedback mail
311 messages. The fancy word for this is ``idempotency''. This simply
312 means that there should be no difference between making a GET request
313 for a particular URL once or multiple times. This is because the
314 HTTP protocol definition says that a GET request may be cached by the
315 browser, or server, or an intervening proxy. POST requests cannot be
316 cached, because each request is independent and matters. Typically,
317 POST requests change or depend on state on the server (query or update
318 a database, send mail, or purchase a computer).
320 =head2 How do I check a valid mail address?
322 You can't, at least, not in real time. Bummer, eh?
324 Without sending mail to the address and seeing whether there's a human
325 on the other hand to answer you, you cannot determine whether a mail
326 address is valid. Even if you apply the mail header standard, you
327 can have problems, because there are deliverable addresses that aren't
328 RFC-822 (the mail header standard) compliant, and addresses that aren't
329 deliverable which are compliant.
331 Many are tempted to try to eliminate many frequently-invalid
332 mail addresses with a simple regexp, such as
333 C</^[\w.-]+\@([\w.-]\.)+\w+$/>. It's a very bad idea. However,
334 this also throws out many valid ones, and says nothing about
335 potential deliverability, so is not suggested. Instead, see
336 http://www.perl.com/CPAN/authors/Tom_Christiansen/scripts/ckaddr.gz ,
337 which actually checks against the full RFC spec (except for nested
338 comments), looks for addresses you may not wish to accept mail to
339 (say, Bill Clinton or your postmaster), and then makes sure that the
340 hostname given can be looked up in the DNS MX records. It's not fast,
341 but it works for what it tries to do.
343 Our best advice for verifying a person's mail address is to have them
344 enter their address twice, just as you normally do to change a password.
345 This usually weeds out typos. If both versions match, send
346 mail to that address with a personal message that looks somewhat like:
348 Dear someuser@host.com,
350 Please confirm the mail address you gave us Wed May 6 09:38:41
351 MDT 1998 by replying to this message. Include the string
352 "Rumpelstiltskin" in that reply, but spelled in reverse; that is,
353 start with "Nik...". Once this is done, your confirmed address will
354 be entered into our records.
356 If you get the message back and they've followed your directions,
357 you can be reasonably assured that it's real.
359 A related strategy that's less open to forgery is to give them a PIN
360 (personal ID number). Record the address and PIN (best that it be a
361 random one) for later processing. In the mail you send, ask them to
362 include the PIN in their reply. But if it bounces, or the message is
363 included via a ``vacation'' script, it'll be there anyway. So it's
364 best to ask them to mail back a slight alteration of the PIN, such as
365 with the characters reversed, one added or subtracted to each digit, etc.
367 =head2 How do I decode a MIME/BASE64 string?
369 The MIME-tools package (available from CPAN) handles this and a lot
370 more. Decoding BASE64 becomes as simple as:
373 $decoded = decode_base64($encoded);
375 A more direct approach is to use the unpack() function's "u"
376 format after minor transliterations:
378 tr#A-Za-z0-9+/##cd; # remove non-base64 chars
379 tr#A-Za-z0-9+/# -_#; # convert to uuencoded format
380 $len = pack("c", 32 + 0.75*length); # compute length byte
381 print unpack("u", $len . $_); # uudecode and print
383 =head2 How do I return the user's mail address?
385 On systems that support getpwuid, the $E<lt> variable and the
386 Sys::Hostname module (which is part of the standard perl distribution),
387 you can probably try using something like this:
390 $address = sprintf('%s@%s', getpwuid($<), hostname);
392 Company policies on mail address can mean that this generates addresses
393 that the company's mail system will not accept, so you should ask for
394 users' mail addresses when this matters. Furthermore, not all systems
395 on which Perl runs are so forthcoming with this information as is Unix.
397 The Mail::Util module from CPAN (part of the MailTools package) provides a
398 mailaddress() function that tries to guess the mail address of the user.
399 It makes a more intelligent guess than the code above, using information
400 given when the module was installed, but it could still be incorrect.
401 Again, the best way is often just to ask the user.
403 =head2 How do I send mail?
405 Use the C<sendmail> program directly:
407 open(SENDMAIL, "|/usr/lib/sendmail -oi -t -odq")
408 or die "Can't fork for sendmail: $!\n";
409 print SENDMAIL <<"EOF";
410 From: User Originating Mail <me\@host>
411 To: Final Destination <you\@otherhost>
412 Subject: A relevant subject line
414 Body of the message goes here, in as many lines as you like.
416 close(SENDMAIL) or warn "sendmail didn't close nicely";
418 The B<-oi> option prevents sendmail from interpreting a line consisting
419 of a single dot as "end of message". The B<-t> option says to use the
420 headers to decide who to send the message to, and B<-odq> says to put
421 the message into the queue. This last option means your message won't
422 be immediately delivered, so leave it out if you want immediate
425 Or use the CPAN module Mail::Mailer:
429 $mailer = Mail::Mailer->new();
430 $mailer->open({ From => $from_address,
434 or die "Can't open: $!\n";
438 The Mail::Internet module uses Net::SMTP which is less Unix-centric than
439 Mail::Mailer, but less reliable. Avoid raw SMTP commands. There
440 are many reasons to use a mail transport agent like sendmail. These
441 include queueing, MX records, and security.
443 =head2 How do I read mail?
445 Use the Mail::Folder module from CPAN
446 (part of the MailFolder package) or the Mail::Internet module from
447 CPAN (also part of the MailTools package).
452 # say which mail host to use
453 $ENV{SMTPHOSTS} = 'mail.frii.com';
455 $header = new Mail::Header;
456 $header->add('From', 'gnat@frii.com');
457 $header->add('Subject', 'Testing');
458 $header->add('To', 'gnat@frii.com');
460 $body = 'This is a test, ignore';
462 $mail = new Mail::Internet(undef, Header => $header, Body => \[$body]);
464 $mail->smtpsend or die;
466 Often a module is overkill, though. Here's a mail sorter.
469 # bysub1 - simple sort by subject
472 $/ = ''; # paragraph reads
475 /^Subject:\s*(?:Re:\s*)*(.*)/mi;
476 $sub[++$msgno] = lc($1) || '';
480 for my $i (sort { $sub[$a] cmp $sub[$b] || $a <=> $b } (0 .. $#msgs)) {
487 # bysub2 - awkish sort-by-subject
488 BEGIN { $msgno = -1 }
489 $sub[++$msgno] = (/^Subject:\s*(?:Re:\s*)*(.*)/mi)[0] if /^From/m;
491 END { print @msg[ sort { $sub[$a] cmp $sub[$b] || $a <=> $b } (0 .. $#msg) ] }
493 =head2 How do I find out my hostname/domainname/IP address?
495 The normal way to find your own hostname is to call the C<`hostname`>
496 program. While sometimes expedient, this has some problems, such as
497 not knowing whether you've got the canonical name or not. It's one of
498 those tradeoffs of convenience versus portability.
500 The Sys::Hostname module (part of the standard perl distribution) will
501 give you the hostname after which you can find out the IP address
502 (assuming you have working DNS) with a gethostbyname() call.
506 my $host = hostname();
507 my $addr = inet_ntoa(scalar(gethostbyname($name)) || 'localhost');
509 Probably the simplest way to learn your DNS domain name is to grok
510 it out of /etc/resolv.conf, at least under Unix. Of course, this
511 assumes several things about your resolv.conf configuration, including
514 (We still need a good DNS domain name-learning method for non-Unix
517 =head2 How do I fetch a news article or the active newsgroups?
519 Use the Net::NNTP or News::NNTPClient modules, both available from CPAN.
520 This can make tasks like fetching the newsgroup list as simple as:
522 perl -MNews::NNTPClient
523 -e 'print News::NNTPClient->new->list("newsgroups")'
525 =head2 How do I fetch/put an FTP file?
527 LWP::Simple (available from CPAN) can fetch but not put. Net::FTP (also
528 available from CPAN) is more complex but can put as well as fetch.
530 =head2 How can I do RPC in Perl?
532 A DCE::RPC module is being developed (but is not yet available), and
533 will be released as part of the DCE-Perl package (available from
534 CPAN). No ONC::RPC module is known.
536 =head1 AUTHOR AND COPYRIGHT
538 Copyright (c) 1997, 1998 Tom Christiansen and Nathan Torkington.
541 When included as part of the Standard Version of Perl, or as part of
542 its complete documentation whether printed or otherwise, this work
543 may be distributed only under the terms of Perl's Artistic License.
544 Any distribution of this file or derivatives thereof I<outside>
545 of that package require that special arrangements be made with
548 Irrespective of its distribution, all code examples in this file
549 are hereby placed into the public domain. You are permitted and
550 encouraged to use this code in your own programs for fun
551 or for profit as you see fit. A simple comment in the code giving
552 credit would be courteous but is not required.