argra****@users*****
argra****@users*****
2011年 3月 21日 (月) 04:05:04 JST
Index: docs/modules/libwww-perl-5.813/lwptut.pod
diff -u docs/modules/libwww-perl-5.813/lwptut.pod:1.1 docs/modules/libwww-perl-5.813/lwptut.pod:1.2
--- docs/modules/libwww-perl-5.813/lwptut.pod:1.1 Fri Mar 11 00:53:12 2011
+++ docs/modules/libwww-perl-5.813/lwptut.pod Mon Mar 21 04:05:04 2011
@@ -27,13 +27,10 @@
LWP ("Library for WWW in Perl" ‚Ì’ZkŒ`) ‚ÍAWeb ã‚̃f[ƒ^‚É
ƒAƒNƒZƒX‚·‚邽‚ß‚Ì”ñí‚É—L–¼‚È Perl ƒ‚ƒWƒ…[ƒ‹ŒQ‚Å‚·B
-Like most Perl
-module-distributions, each of LWP's component modules comes with
-documentation that is a complete reference to its interface. However,
-there are so many modules in LWP that it's hard to know where to start
-looking for information on how to do even the simplest most common
-things.
-(TBT)
+‚Ù‚Æ‚ñ‚Ç‚Ì Perl ƒ‚ƒWƒ…[ƒ‹”z•z‚Æ“¯—lALWP ‚̃Rƒ“ƒ|[ƒlƒ“ƒgƒ‚ƒWƒ…[ƒ‹‚Ì
+‚»‚ꂼ‚ê‚É‚ÍŠ®‘S‚ȃCƒ“ƒ^[ƒtƒF[ƒX‚̃Šƒtƒ@ƒŒƒ“ƒX•¶‘‚ª“¯«‚³‚ê‚Ä‚¢‚Ü‚·B
+‚µ‚©‚µALWP ‚É‚Í‚½‚‚³‚ñ‚̃‚ƒWƒ…[ƒ‹‚ª‚ ‚é‚Ì‚ÅAÅ‚à’Pƒ‚ÅÅ‚àˆê”Ê“I‚È
+‚±‚Æ‚ð‚·‚é‚½‚ß‚Ìî•ñ‚Å‚·‚çA‚Ç‚±‚©‚ç’T‚¹‚΂悢‚Ì‚©‚ª‚í‚©‚è‚É‚‚¢‚Å‚·B
=begin original
@@ -44,11 +41,10 @@
=end original
-Really introducing you to using LWP would require a whole book -- a book
-that just happens to exist, called I<Perl & LWP>. But this article
-should give you a taste of how you can go about some common tasks with
-LWP.
-(TBT)
+LWP ‚ÌŽg‚¢•û‚ðà–¾‚·‚é‚É‚Í–{ 1 û‚ª•K—v‚Å‚· -- ‚½‚Ü‚½‚Ü I<Perl & LWP> ‚Æ‚¢‚¤
+–{‚ª‚ ‚è‚Ü‚·B
+‚µ‚©‚µA‚±‚Ì‹LŽ–‚Í LWP ‚Å‚¢‚‚‚©‚̈ê”Ê“I‚Èì‹Æ‚ð‚·‚é•û–@‚Ì‚³‚í‚è‚ð
+à–¾‚µ‚Ü‚·B
=head2 Getting documents with LWP::Simple
@@ -61,9 +57,8 @@
=end original
-If you just want to get what's at a particular URL, the simplest way
-to do it is LWP::Simple's functions.
-(TBT)
+’P‚É“Á’è‚Ì URL ‚Ì“à—e‚ðŽæ“¾‚µ‚½‚¢‚È‚çAÅ‚àŠÈ’P‚È•û–@‚Í
+LWP::Simple ‚ÌŠÖ”‚ðŽg‚¤‚±‚Æ‚Å‚·B
=begin original
@@ -73,10 +68,10 @@
=end original
-In a Perl program, you can call its C<get($url)> function. It will try
-getting that URL's content. If it works, then it'll return the
-content; but if there's some error, it'll return undef.
-(TBT)
+Perl ƒvƒƒOƒ‰ƒ€’†‚ÅA‚±‚̃‚ƒWƒ…[ƒ‹‚Ì C<get($url)> ŠÖ”‚ðŒÄ‚Ño‚µ‚Ü‚·B
+‚±‚ê‚ÍŽw’肳‚ꂽ URL ‚Ì“à—e‚ðŽæ“¾‚µ‚悤‚Æ‚µ‚Ü‚·B
+‚¤‚Ü‚s‚¯‚ÎA“à—e‚ð•Ô‚µ‚Ü‚·; ‚µ‚©‚µA‚à‚µ‰½‚©ƒGƒ‰[‚ª‹N‚±‚ê‚ÎA
+–¢’è‹`’l‚ð•Ô‚µ‚Ü‚·B
my $url = 'http://freshair.npr.org/dayFA.cfm?todayDate=current';
# Just an example: the URL for the most recent /Fresh Air/ show
@@ -102,10 +97,10 @@
=end original
-The handiest variant on C<get> is C<getprint>, which is useful in Perl
-one-liners. If it can get the page whose URL you provide, it sends it
-to STDOUT; otherwise it complains to STDERR.
-(TBT)
+Å‚à•Ö—˜‚È C<get> ‚̃oƒŠƒG[ƒVƒ‡ƒ“‚Í C<getprint> ‚ÅAPerl 1s–ì˜Y‚Å
+—L—p‚Å‚·B
+Žw’肵‚½ URL ‚©‚çƒy[ƒW‚ðŽæ“¾‚Å‚«‚ê‚ÎA“à—e‚ð STDOUT ‚Éo—Í‚µ‚Ü‚·;
+‚³‚à‚È‚¯‚ê‚Î STDERR ‚ɃGƒ‰[‚ðo—Í‚µ‚Ü‚·B
% perl -MLWP::Simple -e "getprint 'http://cpan.org/RECENT'"
@@ -118,11 +113,10 @@
=end original
-That is the URL of a plaintext file that lists new files in CPAN in
-the past two weeks. You can easily make it part of a tidy little
-shell command, like this one that mails you the list of new
-C<Acme::> modules:
-(TBT)
+‚±‚ê‚Í CPAN “à‚̉ߋŽ 2 TŠÔ‚ÌV‹Kƒtƒ@ƒCƒ‹‚̈ꗗ‚̃vƒŒ[ƒ“ƒeƒLƒXƒgƒtƒ@ƒCƒ‹‚Ì
+URL ‚Å‚·B
+‚±‚ê‚É‚æ‚Á‚Ä‚¿‚å‚Á‚Æ‚µ‚½ƒVƒFƒ‹ƒRƒ}ƒ“ƒh‚̈ꕔ‚Æ‚µ‚ÄŽg‚¦‚Ü‚·;
+—Ⴆ‚Î V‚µ‚¢ C<Acme::> ƒ‚ƒWƒ…[ƒ‹‚̈ꗗ‚ðƒ[ƒ‹‚·‚é‚É‚Í:
% perl -MLWP::Simple -e "getprint 'http://cpan.org/RECENT'" \
| grep "/by-module/Acme" | mail -s "New Acme modules! Joy!" $USER
@@ -138,13 +132,11 @@
=end original
-There are other useful functions in LWP::Simple, including one function
-for running a HEAD request on a URL (useful for checking links, or
-getting the last-revised time of a URL), and two functions for
-saving/mirroring a URL to a local file. See L<the LWP::Simple
-documentation|LWP::Simple> for the full details, or chapter 2 of I<Perl
-& LWP> for more examples.
-(TBT)
+LWP::Simple ‚É‚Í‚»‚Ì‘¼‚É‚à•Ö—˜‚ÈŠÖ”‚ª‚ ‚è‚Ü‚·; URL ‚É HEAD ƒŠƒNƒGƒXƒg‚ð
+‘—‚éŠÖ” (ƒŠƒ“ƒN‚̃`ƒFƒbƒN‚âA‚ ‚é URL ‚ÌÅIXV“úŽž‚̎擾‚É•Ö—˜‚Å‚·) ‚âA
+URL ‚Ì“à—e‚ðƒ[ƒJƒ‹ƒtƒ@ƒCƒ‹‚É•Û‘¶/ƒ~ƒ‰[‚·‚邽‚ß‚Ì“ñ‚‚̊֔‚È‚Ç‚Å‚·B
+Š®‘S‚ÈÚׂɂ‚¢‚Ä‚Í L<the LWP::Simple documentation|LWP::Simple> A
+X‚È‚é—á‚ɂ‚¢‚Ä‚Í I<Perl & LWP> ‚Ì‘æ 2 Í‚ðŽQÆ‚µ‚Ä‚‚¾‚³‚¢B
=for comment
##########################################################################
@@ -164,13 +156,11 @@
=end original
-LWP::Simple's functions are handy for simple cases, but its functions
-don't support cookies or authorization, don't support setting header
-lines in the HTTP request, generally don't support reading header lines
-in the HTTP response (notably the full HTTP error message, in case of an
-error). To get at all those features, you'll have to use the full LWP
-class model.
-(TBT)
+LWP::Simple ‚ÌŠÖ”‚Í’Pƒ‚È󋵂ł͕֗˜‚Å‚·‚ªA‚±‚ÌŠÖ”‚̓NƒbƒL[‚â”FØ‚É
+‘Ήž‚µ‚Ä‚¢‚Ü‚¹‚ñ‚µAHTTP ƒŠƒNƒGƒXƒg‚̃wƒbƒ_s‚ÌÝ’è‚É‚à‘Ήž‚µ‚Ü‚¹‚ñ‚µA
+ˆê”Ê“I‚É‚Í HTTP ƒŒƒXƒ|ƒ“ƒX‚̃wƒbƒ_s‚Ì“Ç‚Ýž‚Ý(“Á‚ÉAƒGƒ‰[Žž‚Ì
+Š®‘S‚È HTTP ƒGƒ‰[ƒƒbƒZ[ƒW)‚à‘Ήž‚µ‚Ä‚¢‚Ü‚¹‚ñB
+‚±‚ê‚ç‚Ì‹@”\‘S‚Ä‚ðŽg‚¤‚É‚ÍAŠ®‘S‚È LWP ƒNƒ‰ƒXƒ‚ƒfƒ‹‚ðŽg‚¤•K—v‚ª‚ ‚è‚Ü‚·B
=begin original
@@ -182,12 +172,11 @@
=end original
-While LWP consists of dozens of classes, the main two that you have to
-understand are L<LWP::UserAgent> and L<HTTP::Response>. LWP::UserAgent
-is a class for "virtual browsers" which you use for performing requests,
-and L<HTTP::Response> is a class for the responses (or error messages)
-that you get back from those requests.
-(TBT)
+LWP ‚Í”\‚̃Nƒ‰ƒX‚Å\¬‚³‚ê‚Ä‚¢‚Ü‚·‚ªA—‰ð‚·‚é•K—v‚ª‚ ‚éŽå‚È“ñ‚‚̂à‚Ì‚Í
+L<LWP::UserAgent> ‚Æ L<HTTP::Response> ‚Å‚·B
+LWP::UserAgent ‚̓ŠƒNƒGƒXƒg‚ðŽÀs‚·‚é‚Æ‚«‚ÉŽg‚¤u‰¼‘zƒuƒ‰ƒEƒUv‚ÅA
+L<HTTP::Response> ‚Í‚»‚̃ŠƒNƒGƒXƒg‚©‚ç•Ô‚³‚ꂽƒŒƒXƒ|ƒ“ƒX(‚ ‚é‚¢‚Í
+ƒGƒ‰[ƒƒbƒZ[ƒW) ‚Ì‚½‚߂̃Nƒ‰ƒX‚Å‚·B
=begin original
@@ -196,9 +185,8 @@
=end original
-The basic idiom is C<< $response = $browser->get($url) >>, or more fully
-illustrated:
-(TBT)
+Šî–{“I‚ÈŠµ—p–@‚Í C<< $response = $browser->get($url) >> ‚ÅA‚à‚¤‚µ
+Š®‘S‚ÉŽ¦‚·‚Æ:
# Early in your program:
@@ -239,12 +227,11 @@
=end original
-There are two objects involved: C<$browser>, which holds an object of
-class LWP::UserAgent, and then the C<$response> object, which is of
-class HTTP::Response. You really need only one browser object per
-program; but every time you make a request, you get back a new
-HTTP::Response object, which will have some interesting attributes:
-(TBT)
+“ñ‚‚̃IƒuƒWƒFƒNƒg‚ªŠÖ‚í‚Á‚Ä‚¢‚Ü‚·: C<$browser> ‚Í LWP::UserAgent ƒNƒ‰ƒX‚Ì
+ƒIƒuƒWƒFƒNƒg‚ð•ÛŽ‚µAC<$response> ƒIƒuƒWƒFƒNƒg‚Í HTTP::Response ƒNƒ‰ƒX‚Å‚·B
+–{“–‚É•K—v‚ȃuƒ‰ƒEƒUƒIƒuƒWƒFƒNƒg‚Í 1 ƒvƒƒOƒ‰ƒ€’†‚Ɉê‚‚¾‚¯‚Å‚·;
+‚µ‚©‚µƒŠƒNƒGƒXƒg‚ðo‚·–ˆ‚ÉV‚µ‚¢ HTTP::Response ƒIƒuƒWƒFƒNƒg‚ª•Ô‚³‚êA
+‚±‚ê‚É‚Í‚¢‚‚‚©‚Ì‹»–¡[‚¢‘®«‚ð•ÛŽ‚µ‚Ä‚¢‚Ü‚·:
=over
@@ -258,10 +245,8 @@
=end original
-A status code indicating
-success or failure
-(which you can test with C<< $response->is_success >>).
-(TBT)
+¬Œ÷‚©Ž¸”s‚©‚ðŽ¦‚µ‚Ä‚¢‚éƒXƒe[ƒ^ƒXƒR[ƒh(C<< $response->is_success >> ‚Å
+ƒeƒXƒg‚Å‚«‚Ü‚·)B
=item *
@@ -274,11 +259,9 @@
=end original
-An HTTP status
-line that is hopefully informative if there's failure (which you can
-see with C<< $response->status_line >>,
-returning something like "404 Not Found").
-(TBT)
+Ž¸”s‚µ‚½‚Æ‚«‚Ìî•ñ‚É‚È‚é‚©‚à‚µ‚ê‚È‚¢ HTTP ƒXƒe[ƒ^ƒXs
+(C<< $response->status_line >> ‚ÅŒ©‚邱‚Æ‚ª‚Å‚«A"404 Not Found" ‚Ì
+‚悤‚È‚à‚Ì‚ª•Ô‚³‚ê‚Ü‚·)B
=item *
@@ -290,10 +273,8 @@
=end original
-A MIME content-type like "text/html", "image/gif",
-"application/xml", etc., which you can see with
-C<< $response->content_type >>
-(TBT)
+"text/html", "image/gif", "application/xml" ‚̂悤‚È MIME ƒRƒ“ƒeƒ“ƒgƒ^ƒCƒv;
+C<< $response->content_type >> ‚ÅŒ©‚邱‚Æ‚ª‚Å‚«‚Ü‚·B
=item *
@@ -306,11 +287,9 @@
=end original
-The actual content of the response, in C<< $response->decoded_content >>.
-If the response is HTML, that's where the HTML source will be; if
-it's a GIF, then C<< $response->decoded_content >> will be the binary
-GIF data.
-(TBT)
+C<< $response->decoded_content >> ‚É‚ ‚郌ƒXƒ|ƒ“ƒX‚ÌŽÀÛ‚Ì“à—eB
+ƒŒƒXƒ|ƒ“ƒX‚ª HTML ‚Ìê‡A‚±‚±‚ª HTML ƒ\[ƒX‚ª“ü‚Á‚Ä‚¢‚éꊂł·;
+GIF ‚Ìê‡AC<< $response->decoded_content >> ‚Í GIF ƒf[ƒ^ƒoƒCƒiƒŠ‚Å‚·B
=item *
@@ -322,10 +301,9 @@
=end original
-And dozens of other convenient and more specific methods that are
-documented in the docs for L<HTML::Response>, and its superclasses
-L<HTML::Message> and L<HTML::Headers>.
-(TBT)
+‚»‚µ‚Ä‚½‚‚³‚ñ‚Ì‚»‚Ì‘¼‚Ì•Ö—˜‚Å‚æ‚è“Á—L‚̃ƒ\ƒbƒh‚ÍA
+L<HTML::Response> ‚¨‚æ‚Ñ‚»‚̃X[ƒp[ƒNƒ‰ƒX‚Å‚ ‚é
+L<HTML::Message> ‚Æ L<HTML::Headers> ‚Ì•¶‘‚Å•¶‘‰»‚³‚ê‚Ä‚¢‚Ü‚·B
=back
@@ -334,6 +312,8 @@
=head2 Adding Other HTTP Request Headers
+(‚»‚Ì‘¼‚Ì HTTP ƒŠƒNƒGƒXƒgƒwƒbƒ_‚ð’ljÁ‚·‚é)
+
=begin original
The most commonly used syntax for requests is C<< $response =
@@ -343,11 +323,10 @@
=end original
-The most commonly used syntax for requests is C<< $response =
-$browser->get($url) >>, but in truth, you can add extra HTTP header
-lines to the request by adding a list of key-value pairs after the URL,
-like so:
-(TBT)
+ƒŠƒNƒGƒXƒg‚Ì‚½‚ß‚ÌÅ‚àˆê”Ê“I‚ÈŽg‚¢•û‚Ì•¶–@‚Í
+C<< $response = $browser->get($url) >> ‚Å‚·‚ªAŽÀÛ‚ÌŠAˆÈ‰º‚̂悤‚ÉA
+URL ‚ÌŒã‚ɃL[/’l‚Ì‘g‚̃ŠƒXƒg‚ð’ljÁ‚·‚邱‚ƂŒljÁ‚Ì HTTP ƒwƒbƒ_‚ð
+’ljÁ‚Å‚«‚Ü‚·:
$response = $browser->get( $url, $key1, $value1, $key2, $value2, ... );
@@ -358,9 +337,8 @@
=end original
-For example, here's how to send some more Netscape-like headers, in case
-you're dealing with a site that would otherwise reject your request:
-(TBT)
+—Ⴆ‚ÎANetscape •—‚̃wƒbƒ_‚È‚µ‚ł̓ŠƒNƒGƒXƒg‚ð‹‘”Û‚·‚éƒTƒCƒg‚ðˆµ‚¤‚½‚ß‚É
+‚»‚̂悤‚ȃwƒbƒ_‚ð’ljÁ‚·‚é‚É‚Í:
my @ns_headers = (
'User-Agent' => 'Mozilla/4.76 [en] (Win98; U)',
@@ -379,8 +357,7 @@
=end original
-If you weren't reusing that array, you could just go ahead and do this:
-(TBT)
+”z—ñ‚ðÄ—˜—p‚µ‚È‚¢‚È‚çA’P‚Ɉȉº‚̂悤‚É‚Å‚«‚Ü‚·:
$response = $browser->get($url,
'User-Agent' => 'Mozilla/4.76 [en] (Win98; U)',
@@ -397,10 +374,9 @@
=end original
-If you were only ever changing the 'User-Agent' line, you could just change
-the C<$browser> object's default line from "libwww-perl/5.65" (or the like)
-to whatever you like, using the LWP::UserAgent C<agent> method:
-(TBT)
+‚à‚µ 'User-Agent' s‚¾‚¯‚ð•ÏX‚·‚é‚È‚çALWP::UserAgent ‚Ì C<agent> ƒƒ\ƒbƒh‚ð
+Žg‚Á‚ÄAC<$browser> ƒIƒuƒWƒFƒNƒg‚̃fƒtƒHƒ‹ƒgs‚Å‚ ‚é
+"libwww-perl/5.65" (‚ ‚é‚¢‚ÍŽ—‚½‚悤‚È‚à‚Ì) ‚©‚çD‚Ý‚Ì‚à‚Ì‚É•ÏX‚Å‚«‚Ü‚·:
$browser->agent('Mozilla/4.76 [en] (Win98; U)');
@@ -424,15 +400,14 @@
=end original
-A default LWP::UserAgent object acts like a browser with its cookies
-support turned off. There are various ways of turning it on, by setting
-its C<cookie_jar> attribute. A "cookie jar" is an object representing
-a little database of all
-the HTTP cookies that a browser can know about. It can correspond to a
-file on disk (the way Netscape uses its F<cookies.txt> file), or it can
-be just an in-memory object that starts out empty, and whose collection of
-cookies will disappear once the program is finished running.
-(TBT)
+ƒfƒtƒHƒ‹ƒg‚Ì LWP::UserAgent ƒIƒuƒWƒFƒNƒg‚ÍAƒNƒbƒL[‘Ήž‚ðƒIƒt‚É‚µ‚½
+ƒuƒ‰ƒEƒU‚̂悤‚ÉU‚é•‘‚¢‚Ü‚·B
+C<cookie_jar> ‘®«‚ðÝ’è‚·‚邱‚Æ‚Å—LŒø‚É‚·‚é‚¢‚‚‚©‚Ì•û–@‚ª‚ ‚è‚Ü‚·B
+uƒNƒbƒL[—eŠív("cookie jar") ‚ÍAƒuƒ‰ƒEƒU‚ª’m‚Á‚Ä‚¢‚é‘S‚Ä‚Ì HTTP
+ƒNƒbƒL[‚̃f[ƒ^ƒx[ƒX‚ð•\Œ»‚·‚éƒIƒuƒWƒFƒNƒg‚Å‚·B
+‚±‚ê‚̓fƒBƒXƒNã‚̃tƒ@ƒCƒ‹ (Netscape ‚ª F<cookies.txt> ƒtƒ@ƒCƒ‹‚Å
+Žg‚Á‚Ä‚¢‚é•û–@)‚©A’P‚É‹ó‚©‚çŠJŽn‚µ‚ăvƒƒOƒ‰ƒ€I—¹Žž‚ÉÁ‚¦‚Ä‚µ‚Ü‚¤
+ƒƒ‚ƒŠã‚̃IƒuƒWƒFƒNƒg‚ɑΉž‚³‚¹‚邱‚Æ‚ª‚Å‚«‚Ü‚·B
=begin original
@@ -441,9 +416,8 @@
=end original
-To give a browser an in-memory empty cookie jar, you set its C<cookie_jar>
-attribute like so:
-(TBT)
+ƒƒ‚ƒŠã‚É‹ó‚̃NƒbƒL[—eŠí‚ðƒuƒ‰ƒEƒU‚ÉÝ’è‚·‚é‚É‚ÍAˆÈ‰º‚̂悤‚É
+C<cookie_jar> ‘®«‚Éݒ肵‚Ü‚·:
$browser->cookie_jar({});
@@ -455,10 +429,8 @@
=end original
-To give it a copy that will be read from a file on disk, and will be saved
-to it when the program is finished running, set the C<cookie_jar> attribute
-like this:
-(TBT)
+ƒfƒBƒXƒNã‚̃tƒ@ƒCƒ‹‚©‚ç“Ç‚Ýž‚ñ‚¾ƒf[ƒ^‚ðŽw’肵‚ÄAƒvƒƒOƒ‰ƒ€I—¹Žž‚É
+•Û‘¶‚·‚邽‚ß‚É‚ÍAC<cookie_jar> ‘®«‚ðˆÈ‰º‚̂悤‚Éݒ肵‚Ü‚·:
use HTTP::Cookies;
$browser->cookie_jar( HTTP::Cookies->new(
@@ -476,10 +448,9 @@
=end original
-That file will be an LWP-specific format. If you want to be access the
-cookies in your Netscape cookies file, you can use the
-HTTP::Cookies::Netscape class:
-(TBT)
+‚±‚̃tƒ@ƒCƒ‹‚Í LWP ŒÅ—L‚ÌŒ`Ž®‚Å‚·B
+Netscape ‚̃NƒbƒL[ƒtƒ@ƒCƒ‹‚̃NƒbƒL[‚ðƒAƒNƒZƒX‚·‚é‚悤‚É‚·‚é‚É‚ÍA
+HTTP::Cookies::Netscape ƒNƒ‰ƒX‚ðŽg‚¦‚Ü‚·:
use HTTP::Cookies;
# yes, loads HTTP::Cookies::Netscape too
@@ -497,10 +468,9 @@
=end original
-You could add an C<< 'autosave' => 1 >> line as further above, but at
-time of writing, it's uncertain whether Netscape might discard some of
-the cookies you could be writing back to disk.
-(TBT)
+ãq‚̂悤‚É C<< 'autosave' => 1 >> s‚ð’ljÁ‚·‚邱‚Æ‚à‚Å‚«‚Ü‚·‚ªA
+‘‚«ž‚ÝŽž‚É Netscape ‚ªƒfƒB“í‚É‘‚«–ß‚»‚¤‚Æ‚µ‚½ƒNƒbƒL[‚̈ꕔ‚ð
+”jŠü‚·‚é‚©‚Ç‚¤‚©‚Í•sŠm’è‚Å‚·B
=for comment
##########################################################################
@@ -516,9 +486,8 @@
=end original
-Many HTML forms send data to their server using an HTTP POST request, which
-you can send with this syntax:
-(TBT)
+‘½‚‚Ì HTML ƒtƒH[ƒ€‚Í HTTP POST ƒŠƒNƒGƒXƒg‚ðŽg‚Á‚ăT[ƒo‚Ƀf[ƒ^‚ð
+‘—‚è‚Ü‚·‚ªA‚±‚ê‚ɂ͈ȉº‚̂悤‚È•¶–@‚ðŽg‚¢‚Ü‚·:
$response = $browser->post( $url,
[
@@ -534,8 +503,7 @@
=end original
-Or if you need to send HTTP headers:
-(TBT)
+‚ ‚é‚¢‚Í HTTP ƒwƒbƒ_‚ð‘—‚é•K—v‚ª‚ ‚éꇂÍ:
$response = $browser->post( $url,
[
@@ -555,10 +523,9 @@
=end original
-For example, the following program makes a search request to AltaVista
-(by sending some form data via an HTTP POST request), and extracts from
-the HTML the report of the number of matches:
-(TBT)
+—Ⴆ‚ÎAˆÈ‰º‚̃vƒƒOƒ‰ƒ€‚Í AltaVista ‚É (ƒtƒH[ƒ€ƒf[ƒ^‚ð HTTP POST
+ƒŠƒNƒGƒXƒgŒo—R‚Å‘—M‚·‚邱‚Æ‚Å) ŒŸõƒŠƒNƒGƒXƒg‚ð‘—‚Á‚ÄAHTML ‚©‚ç
+ƒ}ƒbƒ`ƒ“ƒO‚Ì”‚Ì•ñ‚ð“WŠJ‚µ‚Ü‚·:
use strict;
use warnings;
@@ -619,9 +586,7 @@
=end original
-To run the same search with LWP, you'd use this idiom, which involves
-the URI class:
-(TBT)
+“¯‚¶ŒŸõ‚ð LWP ‚ÅŽÀs‚·‚é‚É‚ÍAURI ‚ðŽg‚Á‚½‚±‚Ì’èŒ^•¶‚ðŽg‚¢‚Ü‚·:
use URI;
my $url = URI->new( 'http://us.imdb.com/Tsearch' );
@@ -642,10 +607,9 @@
=end original
-See chapter 5 of I<Perl & LWP> for a longer discussion of HTML forms
-and of form data, and chapters 6 through 9 for a longer discussion of
-extracting data from HTML.
-(TBT)
+HTML ƒtƒH[ƒ€‚ƃtƒH[ƒ€ƒf[ƒ^‚ÉŠÖ‚·‚é‚æ‚è’·‚¢‹c˜_‚ɂ‚¢‚Ä‚ÍI<Perl & LWP> ‚Ì
+‘æ 5 Í‚ðAHTML ‚©‚ç‚̃f[ƒ^‚Ì’Šo‚ÉŠÖ‚·‚é‚æ‚è’·‚¢‹c˜_‚ɂ‚¢‚Ä‚Í
+‘æ 6 Í‚©‚ç‘æ 9 Í‚ðŽQÆ‚µ‚Ä‚‚¾‚³‚¢B
=head2 Absolutizing URLs
@@ -686,9 +650,8 @@
=end original
-For example, consider this program that matches URLs in the HTML
-list of new modules in CPAN:
-(TBT)
+—Ⴆ‚ÎACPAN ‚ÌV‚µ‚¢ƒ‚ƒWƒ…[ƒ‹‚Ì HTML ƒŠƒXƒg‚É‚ ‚é URL ‚Ƀ}ƒbƒ`ƒ“ƒO‚·‚é
+‚±‚̃vƒƒOƒ‰ƒ€‚ðl‚¦‚Ü‚·:
use strict;
use warnings;
@@ -711,8 +674,7 @@
=end original
-When run, it emits output that starts out something like this:
-(TBT)
+ŽÀs‚·‚é‚ÆA‚±‚̂悤‚È‚à‚Ì‚ðo—Í‚µ‚Ü‚·:
MIRRORING.FROM
RECENT
@@ -730,10 +692,8 @@
=end original
-However, if you actually want to have those be absolute URLs, you
-can use the URI module's C<new_abs> method, by changing the C<while>
-loop to this:
-(TBT)
+‚µ‚©‚µAŽÀÛ‚É‚Íâ‘Î URL ‚ª‚Ù‚µ‚¢ê‡AURI ƒ‚ƒWƒ…[ƒ‹‚Ì
+C<new_abs> ƒƒ\ƒbƒh‚ðŽg‚Á‚ÄAC<while> ƒ‹[ƒv‚ð‚±‚Ì‚æ‚¤‚É•ÏX‚Å‚«‚Ü‚·:
while( $html =~ m/<A HREF=\"(.*?)\"/g ) {
print URI->new_abs( $1, $response->base ) ,"\n";
@@ -748,7 +708,8 @@
=end original
-(The C<< $response->base >> method from L<HTTP::Message|HTTP::Message>
+(L<HTTP::Message|HTTP::Message> ‚Ì C<< $response->base >> ƒƒ\ƒbƒh‚Í
+method from
is for returning what URL
should be used for resolving relative URLs -- it's usually just
the same as the URL that you requested.)