Bir seçenek CURLOPT_POSTFIELDS bulunmaktadır. Bu bir ilişkisel dizi olarak ya da bir dize olarak da POST verileri ayarlamanızı sağlar. Yani, ikinci seçeneği kullanmak gerekir.

Sen yok. Sorgular ve POST veri name=value formu gelir hem de GET. Eğer bir dosya yükleme kontrolü var çünkü enctype="multipart/form-data" bir formun teslim kodlamasını değiştirmek eğer tek istisna değildir.

http://www.cs.tut.fi/~jkorpela/forms/file.html#enctype daha fazla bilgi için bakınız:

HTML spesifikasyonu için iki olası değerler tanımlar enctype:

enctype="application/x-www-form-urlencoded" (the default)
This implies a simple encoding which presents the fields as name=value strings separated by ampersands (&) and uses some special “escape” mechanisms for characters, such as %28 for the “(” character. It’s confusing if people try to read it—it was meant to be processed by programs, not directly read by humans!

enctype="multipart/form-data"
This implies that the form data set is encoded so that each form field (more exactly, each “control”) is presented in a format suitable for that field, and the data set as a whole is a multipart message containing those presentations as its components. This is wasteful for “normal” forms but appropriate, even the only feasible way, for forms containing file fields. The multipart structure means that each file comes in a nice “package” inside a larger package, with a suitable “label” (content type information) on the inner “package.” This type was originally defined in RFC 1867 but it is also discussed in RFC 2388 (see notes on the RFCs later).