summaryrefslogtreecommitdiff
path: root/cpan/File-Fetch
diff options
context:
space:
mode:
authorPeter J. Acklam <pjacklam@online.no>2011-01-06 23:08:02 -0800
committerChris 'BinGOs' Williams <chris@bingosnet.co.uk>2011-01-07 11:15:08 +0000
commit759feaa69fc1e9dbe055a96e49485c33d6bef857 (patch)
tree583b72bb3f8ffbc05088fca758f5d705800bb950 /cpan/File-Fetch
parent1a3aa1dbb2cc3a3973143eb8f10614206525dc1e (diff)
downloadperl-759feaa69fc1e9dbe055a96e49485c33d6bef857.tar.gz
Fix typos (spelling errors) in cpan/File-Fetch/*.
# New Ticket Created by (Peter J. Acklam) # Please include the string: [perl #81802] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=81802 > Signed-off-by: Chris 'BinGOs' Williams <chris@bingosnet.co.uk>
Diffstat (limited to 'cpan/File-Fetch')
-rw-r--r--cpan/File-Fetch/lib/File/Fetch.pm8
1 files changed, 4 insertions, 4 deletions
diff --git a/cpan/File-Fetch/lib/File/Fetch.pm b/cpan/File-Fetch/lib/File/Fetch.pm
index 8bdae35746..2223a5ea3d 100644
--- a/cpan/File-Fetch/lib/File/Fetch.pm
+++ b/cpan/File-Fetch/lib/File/Fetch.pm
@@ -723,7 +723,7 @@ sub _iosock_fetch {
}
# Check the "response"
- # Strip preceeding blank lines apparently they are allowed (RFC 2616 4.1)
+ # Strip preceding blank lines apparently they are allowed (RFC 2616 4.1)
$resp =~ s/^(\x0d?\x0a)+//;
# Check it is an HTTP response
unless ( $resp =~ m!^HTTP/(\d+)\.(\d+)!i ) {
@@ -1087,7 +1087,7 @@ sub _ncftp_fetch {
};
check( $tmpl, \%hash ) or return;
- ### we can only set passive mode in interactive sesssions, so bail out
+ ### we can only set passive mode in interactive sessions, so bail out
### if $FTP_PASSIVE is set
return if $FTP_PASSIVE;
@@ -1256,7 +1256,7 @@ sub _file_fetch {
### prefix a / on unix systems with a file uri, since it would
### look somewhat like this:
### file:///home/kane/file
- ### wheras windows file uris for 'c:\some\dir\file' might look like:
+ ### whereas windows file uris for 'c:\some\dir\file' might look like:
### file:///C:/some/dir/file
### file:///C|/some/dir/file
### or for a network share '\\host\share\some\dir\file':
@@ -1554,7 +1554,7 @@ which we in turn capture. If that content is a 'custom' error file
Sadly, C<lynx> doesn't support any options to return a different exit
code on non-C<200 OK> status, giving us no way to tell the difference
-between a 'successfull' fetch and a custom error page.
+between a 'successful' fetch and a custom error page.
Therefor, we recommend to only use C<lynx> as a last resort. This is
why it is at the back of our list of methods to try as well.