Searched refs:uploads (Results 1 – 16 of 16) sorted by relevance
/curl/tests/http/ |
H A D | scorecard.py | 435 uploads: Optional[List[int]] = None, 480 if uploads and len(uploads) > 0: 481 score['uploads'] = self.uploads(count=upload_count, 482 fsizes=uploads) 725 uploads = [1024 * 1024, 10 * 1024 * 1024, 100 * 1024 * 1024] 727 uploads = [] 729 uploads.extend([parse_size(s) for s in x.split(',')]) 736 if not args.uploads: 737 uploads = None 800 if uploads and httpd is None: [all …]
|
/curl/docs/cmdline-opts/ |
H A D | continue-at.md | 22 source file before it is transferred to the destination. If used with uploads,
|
H A D | anyauth.md | 26 Using --anyauth is not recommended if you do uploads from stdin, since it may
|
H A D | limit-rate.md | 23 and uploads. This feature is useful if you have a limited pipe and you would
|
/curl/tests/data/ |
H A D | test149 | 18 FTP with multiple uploads
|
/curl/docs/libcurl/opts/ |
H A D | CURLOPT_READFUNCTION.md | 21 CURLOPT_READFUNCTION - read callback for data uploads 61 **Bugs**: when doing TFTP uploads, you must return the exact amount of data
|
H A D | CURLOPT_RESUME_FROM.md | 36 When doing uploads with FTP, the resume position is where in the local/source
|
H A D | CURLOPT_RESUME_FROM_LARGE.md | 37 When doing uploads with FTP, the resume position is where in the local/source
|
H A D | CURLOPT_RANGE.md | 50 For HTTP PUT uploads this option should not be used, since it may conflict with
|
H A D | CURLOPT_UPLOAD.md | 32 CURLOPT_INFILESIZE_LARGE(3) options are also interesting for uploads. If the
|
H A D | CURLOPT_HTTPHEADER.md | 43 mail uploads.
|
/curl/docs/libcurl/ |
H A D | libcurl-ws.md | 92 flexible than limited to plain downloads or uploads, libcurl offers two
|
H A D | libcurl-security.md | 213 for uploads. Also, CURLOPT_FOLLOWLOCATION(3) should not be used on 214 uploads. Instead, the applications should consider handling redirects itself, 358 attacker can affect what data the client uploads, it can be made to work as a
|
H A D | libcurl-tutorial.md | 338 A few protocols do not behave properly when uploads are done without any prior 531 and then a file with binary contents and uploads the whole thing. 1440 Transfer-Encoding in cases where HTTP uploads are done with data of an unknown
|
/curl/docs/ |
H A D | KNOWN_BUGS | 34 4.2 -T - always uploads chunked 205 4.2 -T - always uploads chunked
|
H A D | TODO | 727 would be good to offer a way for users to select for uploads to remain
|
Completed in 20 milliseconds