mirror of
https://github.com/curl/curl.git
synced 2026-08-05 11:36:14 +03:00
URLs: change more http to https
This commit is contained in:
parent
742deff4dd
commit
d49881cb19
18 changed files with 46 additions and 44 deletions
2
docs/FAQ
2
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue