Added 3.10 and a few minor updates
diff --git a/docs/FAQ b/docs/FAQ
index 64be0c8..0fad2ed 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -1,4 +1,4 @@
-Updated: February 2, 2001 (http://curl.haxx.se/docs/faq.shtml)
+Updated: February 12, 2001 (http://curl.haxx.se/docs/faq.shtml)
_ _ ____ _
___| | | | _ \| |
/ __| | | | |_) | |
@@ -31,6 +31,7 @@
3.7 Can I use curl to delete/rename a file through FTP?
3.8 How do I tell curl to follow HTTP redirects?
3.9 How do I use curl in PHP?
+ 3.10 What about SOAP, WEBDAV, XML-RPC or similar protocols over HTTP?
4. Running Problems
4.1 Problems connecting to SSL servers.
@@ -106,8 +107,8 @@
or with PHP.
Curl is not a single-OS program. Curl exists, compiles, builds and runs
- under a wide range of operating systems, including all modern Unixes,
- Windows, Amiga, BeOS, OS/2, OS X, QNX etc.
+ under a wide range of operating systems, including all modern Unixes (and a
+ bunch of older ones too), Windows, Amiga, BeOS, OS/2, OS X, QNX etc.
1.4 When will you make curl do XXXX ?
@@ -230,7 +231,7 @@
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', than and only then you must
+ "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
causes a posting with the type 'application/x-www-form-urlencoded'.
@@ -294,6 +295,16 @@
invoke the curl tool using a command line. This is the way to use curl if
you're using PHP3 or PHP4 built without curl module support.
+ 3.10 What about SOAP, WEBDAV, XML-RPC or similar protocols over HTTP?
+
+ Curl adheres to the HTTP spec, which basically means you can play with *any*
+ protocol that is built ontop of HTTP. Protocols such as SOAP, WEBDAV and
+ XML-RPC are all such ones. You can use -X to set custom requests and -H to
+ set custom headers (or replace internally generated ones).
+
+ Using libcurl or PHP's curl modules is just as fine and you'd just use the
+ proper library options to do the same.
+
4. Running Problems
4.1. Problems connecting to SSL servers.
@@ -426,7 +437,8 @@
4.9. Curl can't authenticate to the server that requires NTLM?
NTLM is a Microsoft proprietary protocol. Unfortunately, curl does not
- currently support that.
+ currently support that. Proprietary formats are evil. You should not use
+ such ones.
5. libcurl Issues
@@ -512,7 +524,7 @@
6. License Issues
- NOTE: This section is now updated to concern curl 7.5.2 or later!
+ NOTE: This section concerns curl 7.5.2 or later!
Curl and libcurl are released under a MIT/X derivate license *or* the MPL,
the Mozilla Public License. To get a really good answer to your license
@@ -530,27 +542,25 @@
6.2. I have a closed-source program, can I use the libcurl library?
- Yes.
+ Yes!
- libcurl does not put any restrictions on the program that uses the
- library.
+ libcurl does not put any restrictions on the program that uses the library.
6.3. I have a BSD licensed program, can I use the libcurl library?
- Yes.
+ Yes!
- libcurl does not put any restrictions on the program that uses the
- library.
+ libcurl does not put any restrictions on the program that uses the library.
6.4. I have a program that uses LGPL libraries, can I use libcurl?
- Yes.
+ Yes!
- The LGPL license don't clash with other licenses.
+ The LGPL license doesn't clash with other licenses.
6.5. Can I modify curl/libcurl for my program and keep the changes secret?
- Yes.
+ Yes!
The MIT/X derivate license practically allows you to do almost anything with
the sources, on the condition that the copyright texts in the sources are
@@ -558,9 +568,11 @@
6.6. Can you please change the curl/libcurl license to XXXX?
- No. We carefully picked this license years ago and a large amount of people
- have contributed with source code knowing that this is the license we
- use. This license puts the restrictions we want on curl/libcurl and it does
- not spread to other programs or libraries that use it. The recent dual
- license modification should make it possible for everyone to use libcurl or
- curl in their projects, no matter what license they already have in use.
+ No.
+
+ We carefully picked this license years ago and a large amount of people have
+ contributed with source code knowing that this is the license we use. This
+ license puts the restrictions we want on curl/libcurl and it does not spread
+ to other programs or libraries that use it. The recent dual license
+ modification should make it possible for everyone to use libcurl or curl in
+ their projects, no matter what license they already have in use.
