aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorViktor Szakats <vszakats@users.noreply.github.com>2016-02-03 05:09:25 +0100
committerJay Satiro <raysatiro@yahoo.com>2016-02-04 18:46:54 -0500
commitd49881cb19971c058eca4a41317b6487bf939e5c (patch)
tree3bad566d3db17bf714868284dd1e1c5ed70bc436 /docs
parent742deff4dddde519e8928c7b13a66a51e83383f1 (diff)
URLs: change more http to https
Diffstat (limited to 'docs')
-rw-r--r--docs/FAQ2
-rw-r--r--docs/libcurl/libcurl-tutorial.32
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/FAQ b/docs/FAQ
index 334dbf3f1..b3035eea5 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -1402,7 +1402,7 @@ FAQ
to do "LIST -a" or similar to see them.
The application thus needs to parse the LIST output. One such existing
- list parser is available at http://cr.yp.to/ftpparse.html Versions of
+ list parser is available at https://cr.yp.to/ftpparse.html Versions of
libcurl since 7.21.0 also provide the ability to specify a wildcard to
download multiple files from one FTP directory.
diff --git a/docs/libcurl/libcurl-tutorial.3 b/docs/libcurl/libcurl-tutorial.3
index 3c9bb60f4..3144da3c6 100644
--- a/docs/libcurl/libcurl-tutorial.3
+++ b/docs/libcurl/libcurl-tutorial.3
@@ -1046,7 +1046,7 @@ input from potentially untrusted users. Following is a discussion about
some risks in the ways in which applications commonly use libcurl and
potential mitigations of those risks. It is by no means comprehensive, but
shows classes of attacks that robust applications should consider. The
-Common Weakness Enumeration project at http://cwe.mitre.org/ is a good
+Common Weakness Enumeration project at https://cwe.mitre.org/ is a good
reference for many of these and similar types of weaknesses of which
application writers should be aware.