FAQ: refreshed some phrases
This commit is contained in:
Родитель
9613cf7211
Коммит
07f97809b8
39
docs/FAQ
39
docs/FAQ
|
@ -245,10 +245,10 @@ FAQ
|
|||
supervised in any way by the project.
|
||||
|
||||
We still get help from companies. Haxx provides web site, bandwidth, mailing
|
||||
lists etc and sourceforge.net hosts project services we take advantage from,
|
||||
like the bug tracker. Also again, some companies have sponsored certain
|
||||
parts of the development in the past and I hope some will continue to do so
|
||||
in the future.
|
||||
lists etc, sourceforge.net hosts project services we take advantage from,
|
||||
like the bug tracker and github hosts the primary git repository. Also
|
||||
again, some companies have sponsored certain parts of the development in the
|
||||
past and I hope some will continue to do so in the future.
|
||||
|
||||
If you want to support our project, consider a donation or a banner-program
|
||||
or even better: by helping us coding, documenting, testing etc.
|
||||
|
@ -309,17 +309,16 @@ FAQ
|
|||
never use it.
|
||||
|
||||
In May 2012 Daniel did a counting game and came up with a number that may
|
||||
be completely wrong or somewhat accurate. 300 million!
|
||||
be completely wrong or somewhat accurate. Over 500 million!
|
||||
|
||||
See http://daniel.haxx.se/blog/2012/05/16/300m-users/
|
||||
|
||||
1.11 Why don't you update ca-bundle.crt
|
||||
|
||||
The ca-bundle.crt file that used to be bundled with curl was very outdated
|
||||
(it being last modified year 2000 should tell) and must be replaced with a
|
||||
much more modern and up-to-date version by anyone who wants to verify peers
|
||||
anyway. It is no longer provided, the last curl release that shipped it was
|
||||
curl 7.18.0.
|
||||
The ca cert bundle that used to shipped with curl was very outdated and must
|
||||
be replaced with an up-to-date version by anyone who wants to verify
|
||||
peers. It is no longer provided by curl. The last curl release ever that
|
||||
shipped a ca cert bundle was curl 7.18.0.
|
||||
|
||||
In the cURL project we've decided not to attempt to keep this file updated
|
||||
(or even present anymore) since deciding what to add to a ca cert bundle is
|
||||
|
@ -433,10 +432,10 @@ FAQ
|
|||
|
||||
That is an OpenSSL binary built for Windows.
|
||||
|
||||
Curl uses OpenSSL to do the SSL stuff. The LIBEAY32.DLL is what curl needs
|
||||
on a windows machine to do https://. Check out the curl web site to find
|
||||
accurate and up-to-date pointers to recent OpenSSL DLLs and other binary
|
||||
packages.
|
||||
Curl can be built with OpenSSL to do the SSL stuff. The LIBEAY32.DLL is then
|
||||
what curl needs on a windows machine to do https:// etc. Check out the curl
|
||||
web site to find accurate and up-to-date pointers to recent OpenSSL DLLs and
|
||||
other binary packages.
|
||||
|
||||
2.4 Does curl support SOCKS (RFC 1928) ?
|
||||
|
||||
|
@ -472,9 +471,9 @@ FAQ
|
|||
3.3 Why doesn't my posting using -F work?
|
||||
|
||||
You can't simply use -F or -d at your choice. The web server that will
|
||||
receive your post assumes one of the formats. If the form you're trying to
|
||||
"fake" sets the type to 'multipart/form-data', then and only then you must
|
||||
use the -F type. In all the most common cases, you should use -d which then
|
||||
receive your post expects one of the formats. If the form you're trying to
|
||||
submit uses the type 'multipart/form-data', then and only then you must use
|
||||
the -F type. In all the most common cases, you should use -d which then
|
||||
causes a posting with the type 'application/x-www-form-urlencoded'.
|
||||
|
||||
This is described in some detail in the MANUAL and TheArtOfHttpScripting
|
||||
|
@ -502,9 +501,9 @@ FAQ
|
|||
3.6 Does curl support ASP, XML, XHTML or HTML version Y?
|
||||
|
||||
To curl, all contents are alike. It doesn't matter how the page was
|
||||
generated. It may be ASP, PHP, Perl, shell-script, SSI or plain
|
||||
HTML-files. There's no difference to curl and it doesn't even know what kind
|
||||
of language that generated the page.
|
||||
generated. It may be ASP, PHP, Perl, shell-script, SSI or plain HTML
|
||||
files. There's no difference to curl and it doesn't even know what kind of
|
||||
language that generated the page.
|
||||
|
||||
See also item 3.14 regarding javascript.
|
||||
|
||||
|
|
Загрузка…
Ссылка в новой задаче