1=head1 NAME
2
3perlfaq9 - Web, Email and Networking
4
5=head1 DESCRIPTION
6
7This section deals with questions related to running web sites,
8sending and receiving email as well as general networking.
9
10=head2 Should I use a web framework?
11
12Yes. If you are building a web site with any level of interactivity
13(forms / users / databases), you
14will want to use a framework to make handling requests
15and responses easier.
16
17If there is no interactivity then you may still want
18to look at using something like L<Template Toolkit|https://metacpan.org/module/Template>
19or L<Plack::Middleware::TemplateToolkit>
20so maintenance of your HTML files (and other assets) is easier.
21
22=head2 Which web framework should I use?
23X<framework> X<CGI.pm> X<CGI> X<Catalyst> X<Dancer>
24
25There is no simple answer to this question. Perl frameworks can run everything
26from basic file servers and small scale intranets to massive multinational
27multilingual websites that are the core to international businesses.
28
29Below is a list of a few frameworks with comments which might help you in
30making a decision, depending on your specific requirements. Start by reading
31the docs, then ask questions on the relevant mailing list or IRC channel.
32
33=over 4
34
35=item L<Catalyst>
36
37Strongly object-oriented and fully-featured with a long development history and
38a large community and addon ecosystem. It is excellent for large and complex
39applications, where you have full control over the server.
40
41=item L<Dancer>
42
43Young and free of legacy weight, providing a lightweight and easy to learn API.
44Has a growing addon ecosystem. It is best used for smaller projects and
45very easy to learn for beginners.
46
47=item L<Mojolicious>
48
49Fairly young with a focus on HTML5 and real-time web technologies such as
50WebSockets.
51
52=item L<Web::Simple>
53
54Currently experimental, strongly object-oriented, built for speed and intended
55as a toolkit for building micro web apps, custom frameworks or for tieing
56together existing Plack-compatible web applications with one central dispatcher.
57
58=back
59
60All of these interact with or use L<Plack> which is worth understanding
61the basics of when building a website in Perl (there is a lot of useful
62L<Plack::Middleware|https://metacpan.org/search?q=plack%3A%3Amiddleware>).
63
64=head2 What is Plack and PSGI?
65
66L<PSGI> is the Perl Web Server Gateway Interface Specification, it is
67a standard that many Perl web frameworks use, you should not need to
68understand it to build a web site, the part you might want to use is L<Plack>.
69
70L<Plack> is a set of tools for using the PSGI stack. It contains
71L<middleware|https://metacpan.org/search?q=plack%3A%3Amiddleware>
72components, a reference server and utilities for Web application frameworks.
73Plack is like Ruby's Rack or Python's Paste for WSGI.
74
75You could build a web site using L<Plack> and your own code,
76but for anything other than a very basic web site, using a web framework
77(that uses L<Plack>) is a better option.
78
79=head2 How do I remove HTML from a string?
80
81Use L<HTML::Strip>, or L<HTML::FormatText> which not only removes HTML
82but also attempts to do a little simple formatting of the resulting
83plain text.
84
85=head2 How do I extract URLs?
86
87L<HTML::SimpleLinkExtor> will extract URLs from HTML, it handles anchors,
88images, objects, frames, and many other tags that can contain a URL.
89If you need anything more complex, you can create your own subclass of
90L<HTML::LinkExtor> or L<HTML::Parser>. You might even use
91L<HTML::SimpleLinkExtor> as an example for something specifically
92suited to your needs.
93
94You can use L<URI::Find> to extract URLs from an arbitrary text document.
95
96=head2 How do I fetch an HTML file?
97
98(contributed by brian d foy)
99
100Use the libwww-perl distribution. The L<LWP::Simple> module can fetch web
101resources and give their content back to you as a string:
102
103    use LWP::Simple qw(get);
104
105    my $html = get( "http://www.example.com/index.html" );
106
107It can also store the resource directly in a file:
108
109    use LWP::Simple qw(getstore);
110
111    getstore( "http://www.example.com/index.html", "foo.html" );
112
113If you need to do something more complicated, you can use
114L<LWP::UserAgent> module to create your own user-agent (e.g. browser)
115to get the job done. If you want to simulate an interactive web
116browser, you can use the L<WWW::Mechanize> module.
117
118=head2 How do I automate an HTML form submission?
119
120If you are doing something complex, such as moving through many pages
121and forms or a web site, you can use L<WWW::Mechanize>. See its
122documentation for all the details.
123
124If you're submitting values using the GET method, create a URL and encode
125the form using the C<query_form> method:
126
127    use LWP::Simple;
128    use URI::URL;
129
130    my $url = url('L<http://www.perl.com/cgi-bin/cpan_mod')>;
131    $url->query_form(module => 'DB_File', readme => 1);
132    $content = get($url);
133
134If you're using the POST method, create your own user agent and encode
135the content appropriately.
136
137    use HTTP::Request::Common qw(POST);
138    use LWP::UserAgent;
139
140    my $ua = LWP::UserAgent->new();
141    my $req = POST 'L<http://www.perl.com/cgi-bin/cpan_mod'>,
142                   [ module => 'DB_File', readme => 1 ];
143    my $content = $ua->request($req)->as_string;
144
145=head2 How do I decode or create those %-encodings on the web?
146X<URI> X<URI::Escape> X<RFC 2396>
147
148Most of the time you should not need to do this as
149your web framework, or if you are making a request,
150the L<LWP> or other module would handle it for you.
151
152To encode a string yourself, use the L<URI::Escape> module. The C<uri_escape>
153function returns the escaped string:
154
155    my $original = "Colon : Hash # Percent %";
156
157    my $escaped = uri_escape( $original );
158
159    print "$escaped\n"; # 'Colon%20%3A%20Hash%20%23%20Percent%20%25'
160
161To decode the string, use the C<uri_unescape> function:
162
163    my $unescaped = uri_unescape( $escaped );
164
165    print $unescaped; # back to original
166
167Remember not to encode a full URI, you need to escape each
168component separately and then join them together.
169
170=head2 How do I redirect to another page?
171
172Most Perl Web Frameworks will have a mechanism for doing this,
173using the L<Catalyst> framework it would be:
174
175    $c->res->redirect($url);
176    $c->detach();
177
178If you are using Plack (which most frameworks do), then
179L<Plack::Middleware::Rewrite> is worth looking at if you
180are migrating from Apache or have URL's you want to always
181redirect.
182
183=head2 How do I put a password on my web pages?
184
185See if the web framework you are using has an
186authentication system and if that fits your needs.
187
188Alternativly look at L<Plack::Middleware::Auth::Basic>,
189or one of the other L<Plack authentication|https://metacpan.org/search?q=plack+auth>
190options.
191
192=head2 How do I make sure users can't enter values into a form that causes my CGI script to do bad things?
193
194(contributed by brian d foy)
195
196You can't prevent people from sending your script bad data. Even if
197you add some client-side checks, people may disable them or bypass
198them completely. For instance, someone might use a module such as
199L<LWP> to submit to your web site. If you want to prevent data that
200try to use SQL injection or other sorts of attacks (and you should
201want to), you have to not trust any data that enter your program.
202
203The L<perlsec> documentation has general advice about data security.
204If you are using the L<DBI> module, use placeholder to fill in data.
205If you are running external programs with C<system> or C<exec>, use
206the list forms. There are many other precautions that you should take,
207too many to list here, and most of them fall under the category of not
208using any data that you don't intend to use. Trust no one.
209
210=head2 How do I parse a mail header?
211
212Use the L<Email::MIME> module. It's well-tested and supports all the
213craziness that you'll see in the real world (comment-folding whitespace,
214encodings, comments, etc.).
215
216  use Email::MIME;
217
218  my $message = Email::MIME->new($rfc2822);
219  my $subject = $message->header('Subject');
220  my $from    = $message->header('From');
221
222If you've already got some other kind of email object, consider passing
223it to L<Email::Abstract> and then using its cast method to get an
224L<Email::MIME> object:
225
226  my $mail_message_object = read_message();
227  my $abstract = Email::Abstract->new($mail_message_object);
228  my $email_mime_object = $abstract->cast('Email::MIME');
229
230=head2 How do I check a valid mail address?
231
232(partly contributed by Aaron Sherman)
233
234This isn't as simple a question as it sounds. There are two parts:
235
236a) How do I verify that an email address is correctly formatted?
237
238b) How do I verify that an email address targets a valid recipient?
239
240Without sending mail to the address and seeing whether there's a human
241on the other end to answer you, you cannot fully answer part I<b>, but
242the L<Email::Valid> module will do both part I<a> and part I<b> as far
243as you can in real-time.
244
245Our best advice for verifying a person's mail address is to have them
246enter their address twice, just as you normally do to change a
247password. This usually weeds out typos. If both versions match, send
248mail to that address with a personal message. If you get the message
249back and they've followed your directions, you can be reasonably
250assured that it's real.
251
252A related strategy that's less open to forgery is to give them a PIN
253(personal ID number). Record the address and PIN (best that it be a
254random one) for later processing. In the mail you send, include a link to
255your site with the PIN included. If the mail bounces, you know it's not
256valid. If they don't click on the link, either they forged the address or
257(assuming they got the message) following through wasn't important so you
258don't need to worry about it.
259
260=head2 How do I decode a MIME/BASE64 string?
261
262The L<MIME::Base64> package handles this as well as the MIME/QP encoding.
263Decoding base 64 becomes as simple as:
264
265    use MIME::Base64;
266    my $decoded = decode_base64($encoded);
267
268The L<Email::MIME> module can decode base 64-encoded email message parts
269transparently so the developer doesn't need to worry about it.
270
271=head2 How do I find the user's mail address?
272
273Ask them for it. There are so many email providers available that it's
274unlikely the local system has any idea how to determine a user's email address.
275
276The exception is for organization-specific email (e.g. foo@yourcompany.com)
277where policy can be codified in your program. In that case, you could look at
278$ENV{USER}, $ENV{LOGNAME}, and getpwuid($<) in scalar context, like so:
279
280  my $user_name = getpwuid($<)
281
282But you still cannot make assumptions about whether this is correct, unless
283your policy says it is. You really are best off asking the user.
284
285=head2 How do I send email?
286
287Use the L<Email::MIME> and L<Email::Sender::Simple> modules, like so:
288
289  # first, create your message
290  my $message = Email::MIME->create(
291    header_str => [
292      From    => 'you@example.com',
293      To      => 'friend@example.com',
294      Subject => 'Happy birthday!',
295    ],
296    attributes => {
297      encoding => 'quoted-printable',
298      charset  => 'utf-8',
299    },
300    body_str => "Happy birthday to you!\n",
301  );
302
303  use Email::Sender::Simple qw(sendmail);
304  sendmail($message);
305
306By default, L<Email::Sender::Simple> will try `sendmail` first, if it exists
307in your $PATH. This generally isn't the case. If there's a remote mail
308server you use to send mail, consider investigating one of the Transport
309classes. At time of writing, the available transports include:
310
311=over 4
312
313=item L<Email::Sender::Transport::Sendmail>
314
315This is the default. If you can use the L<mail(1)> or L<mailx(1)>
316program to send mail from the machine where your code runs, you should
317be able to use this.
318
319=item L<Email::Sender::Transport::SMTP>
320
321This transport contacts a remote SMTP server over TCP. It optionally
322uses SSL and can authenticate to the server via SASL.
323
324=item L<Email::Sender::Transport::SMTP::TLS>
325
326This is like the SMTP transport, but uses TLS security. You can
327authenticate with this module as well, using any mechanisms your server
328supports after STARTTLS.
329
330=back
331
332Telling L<Email::Sender::Simple> to use your transport is straightforward.
333
334  sendmail(
335    $message,
336    {
337      transport => $email_sender_transport_object,
338    }
339  );
340
341=head2 How do I use MIME to make an attachment to a mail message?
342
343L<Email::MIME> directly supports multipart messages. L<Email::MIME>
344objects themselves are parts and can be attached to other L<Email::MIME>
345objects. Consult the L<Email::MIME> documentation for more information,
346including all of the supported methods and examples of their use.
347
348=head2 How do I read email?
349
350Use the L<Email::Folder> module, like so:
351
352  use Email::Folder;
353
354  my $folder = Email::Folder->new('/path/to/email/folder');
355  while(my $message = $folder->next_message) {
356    # next_message returns Email::Simple objects, but we want
357    # Email::MIME objects as they're more robust
358    my $mime = Email::MIME->new($message->as_string);
359  }
360
361There are different classes in the L<Email::Folder> namespace for
362supporting various mailbox types. Note that these modules are generally
363rather limited and only support B<reading> rather than writing.
364
365=head2 How do I find out my hostname, domainname, or IP address?
366X<hostname, domainname, IP address, host, domain, hostfqdn, inet_ntoa,
367gethostbyname, Socket, Net::Domain, Sys::Hostname>
368
369(contributed by brian d foy)
370
371The L<Net::Domain> module, which is part of the Standard Library starting
372in Perl 5.7.3, can get you the fully qualified domain name (FQDN), the host
373name, or the domain name.
374
375    use Net::Domain qw(hostname hostfqdn hostdomain);
376
377    my $host = hostfqdn();
378
379The L<Sys::Hostname> module, part of the Standard Library, can also get the
380hostname:
381
382    use Sys::Hostname;
383
384    $host = hostname();
385
386
387The L<Sys::Hostname::Long> module takes a different approach and tries
388harder to return the fully qualified hostname:
389
390  use Sys::Hostname::Long 'hostname_long';
391
392  my $hostname = hostname_long();
393
394To get the IP address, you can use the C<gethostbyname> built-in function
395to turn the name into a number. To turn that number into the dotted octet
396form (a.b.c.d) that most people expect, use the C<inet_ntoa> function
397from the L<Socket> module, which also comes with perl.
398
399    use Socket;
400
401    my $address = inet_ntoa(
402        scalar gethostbyname( $host || 'localhost' )
403    );
404
405=head2 How do I fetch/put an (S)FTP file?
406
407L<Net::FTP>, and L<Net::SFTP> allow you to interact with FTP and SFTP (Secure
408FTP) servers.
409
410=head2 How can I do RPC in Perl?
411
412Use one of the RPC modules( L<https://metacpan.org/search?q=RPC> ).
413
414=head1 AUTHOR AND COPYRIGHT
415
416Copyright (c) 1997-2010 Tom Christiansen, Nathan Torkington, and
417other authors as noted. All rights reserved.
418
419This documentation is free; you can redistribute it and/or modify it
420under the same terms as Perl itself.
421
422Irrespective of its distribution, all code examples in this file
423are hereby placed into the public domain. You are permitted and
424encouraged to use this code in your own programs for fun
425or for profit as you see fit. A simple comment in the code giving
426credit would be courteous but is not required.
427