Searched refs:requests (Results 1 – 25 of 87) sorted by relevance
1234
6 Help: IPv4 address to use for DNS requests21 Bind to a specific IP address when making IPv4 DNS requests, so that the DNS22 requests originate from this address. The argument should be a single IPv4
6 Help: IPv6 address to use for DNS requests21 Bind to a specific IP address when making IPv6 DNS requests, so that the DNS22 requests originate from this address. The argument should be a single IPv6
6 Help: Interface to use for DNS requests21 Send outgoing DNS requests through the given interface. This option is a
20 Violate RFC 7231/6.4.4 and do not convert POST requests into GET requests when
20 Respect RFC 7231/6.4.2 and do not convert POST requests into GET requests when
20 Respect RFC 7231/6.4.3 and do not convert POST requests into GET requests when
22 Issue a non-TLS HTTP requests using HTTP/2 directly without HTTP/1.1 Upgrade.24 HTTPS requests still do HTTP/2 the standard way with negotiated protocol
24 allows you to send several URL requests, each with their own specific options,25 for example, such as different usernames or custom requests for each.
29 and explanations. Common additional HTTP requests include *PUT* and *DELETE*,34 *PUT* requests are rather invoked by using dedicated command line options.40 The method string you set with --request is used for all requests, which
23 but is for proxy communication only like in CONNECT requests when you want a31 Headers specified with this option are not included in requests that curl
18 Do not to send TFTP options requests. This improves interop with some legacy
17 CURLMOPT_MAX_PIPELINE_LENGTH - maximum number of requests in a pipeline33 outstanding requests in an HTTP/1.1 pipeline. This option is only used for39 number of requests in-flight is CURLMOPT_MAX_HOST_CONNECTIONS(3) *
16 CURLOPT_TFTP_NO_OPTIONS - send no TFTP options requests29 RFC 2348 and RFC 2349 from read and write requests.60 /* do not send TFTP options requests */
45 Enforce HTTP 1.0 requests.49 Enforce HTTP 1.1 requests.53 Attempt HTTP 2 requests. libcurl falls back to HTTP 1.1 if HTTP 2 cannot be71 Issue non-TLS HTTP requests using HTTP/2 without HTTP/1.1 Upgrade. It requires72 prior knowledge that the server supports HTTP/2 straight away. HTTPS requests
54 Instead of GET or HEAD when performing HTTP based requests. This is67 in many cases, it might cause libcurl to send invalid requests and it could79 Instead of LIST when issuing IMAP based requests.83 Instead of LIST and RETR when issuing POP3 based requests.94 Instead of a **HELP** or **VRFY** when issuing SMTP based requests.
32 requests. This is so far only for HTTP requests. Note that this may be more
36 6.4.2 to 6.4.4) and not convert POST requests into GET requests when following
37 it allows CONNECT requests to and often only port 80 and 443 are allowed.43 libcurl convert non-HTTP requests to HTTP when using an HTTP proxy without
5 # This workflow will triage pull requests and apply a label based on the21 pull-requests: write
22 HTTP/1.1 429 too many requests36 HTTP/1.1 429 too many requests47 HTTP/1.1 429 too many requests
14 HTTP/1.1 429 too many requests swsbounce29 HTTP/1.1 429 too many requests swsbounce
5 multiple HTTP requests
47 # requires IPv6 so that we can assume and compare both DoH requests66 # To make the test ignore the order of the two outgoing DoH requests, strip
27 TFTP retrieve without TFTP options requests
82 if(request > data->state.requests) in curl_easy_header()85 request = data->state.requests; in curl_easy_header()140 if(request > data->state.requests) in curl_easy_nextheader()143 request = data->state.requests; in curl_easy_nextheader()327 hs->request = data->state.requests; in Curl_headers_push()
Completed in 69 milliseconds