summaryrefslogtreecommitdiff
path: root/www/p5-HTTP-SimpleLinkChecker
diff options
context:
space:
mode:
authorDmitry Marakasov <amdmi3@FreeBSD.org>2016-05-19 10:53:05 +0000
committerDmitry Marakasov <amdmi3@FreeBSD.org>2016-05-19 10:53:05 +0000
commit1f8b48b772b2d0ac0ed48a8259d2117ea3236a90 (patch)
tree06f11bc7b351f3abf3bf5507405afdba5374614e /www/p5-HTTP-SimpleLinkChecker
parent- Fix trailing whitespace in pkg-descrs, categories [g-n]* (diff)
- Fix trailing whitespace in pkg-descrs, categories [p-x]*
Approved by: portmgr blanket
Diffstat (limited to 'www/p5-HTTP-SimpleLinkChecker')
-rw-r--r--www/p5-HTTP-SimpleLinkChecker/pkg-descr30
1 files changed, 15 insertions, 15 deletions
diff --git a/www/p5-HTTP-SimpleLinkChecker/pkg-descr b/www/p5-HTTP-SimpleLinkChecker/pkg-descr
index 485b6dcfcd7e..e83ca1fbfc18 100644
--- a/www/p5-HTTP-SimpleLinkChecker/pkg-descr
+++ b/www/p5-HTTP-SimpleLinkChecker/pkg-descr
@@ -1,20 +1,20 @@
-You don't have to know anything about objected-oriented Perl, LWP, or the
-HTTP module to be able to check your links. This module is designed for
-the casual user. It has one function, check_link, that returns the HTTP
-response code that it receives when it tries to fetch the web address
-passed to it. The undef value is returned for any non-HTTP failure and the
+You don't have to know anything about objected-oriented Perl, LWP, or the
+HTTP module to be able to check your links. This module is designed for
+the casual user. It has one function, check_link, that returns the HTTP
+response code that it receives when it tries to fetch the web address
+passed to it. The undef value is returned for any non-HTTP failure and the
$HTTP::SimpleLinkChecker::ERROR variable is set.
-The HEAD method is tried first, although if anything other than a good
-status code (those less than 400) is received, another request is made
-with the GET method. Note, however, that even with the best code, no
-module can control how servers decide to respond to a check, or control
-any of the myriad things that can go wrong with the network between you
-and the remote server. Some may filter requests based on origin IP
-address, user-agent type, or any other arbitrary factor. Some servers may
-not respond correctly at all. Furthermore, some servers might be
-temporarily down or overloaded. I recommend that you recheck "broken"
-links a couple times over a long period (like a day or two) before you
+The HEAD method is tried first, although if anything other than a good
+status code (those less than 400) is received, another request is made
+with the GET method. Note, however, that even with the best code, no
+module can control how servers decide to respond to a check, or control
+any of the myriad things that can go wrong with the network between you
+and the remote server. Some may filter requests based on origin IP
+address, user-agent type, or any other arbitrary factor. Some servers may
+not respond correctly at all. Furthermore, some servers might be
+temporarily down or overloaded. I recommend that you recheck "broken"
+links a couple times over a long period (like a day or two) before you
decide they are really broken.
WWW: http://search.cpan.org/dist/HTTP-SimpleLinkChecker/