Searched refs:cause (Results 1 – 25 of 48) sorted by relevance
12
20 the given HTTP proxy. This might cause an extra request/response round-trip.
20 so setting this range to something too narrow might cause unnecessary
20 this option is not used, the TLS layer may use workarounds known to cause
20 use workarounds known to cause interoperability problems with some older
52 Most ECH related errors cause error *CURLE_ECH_REQUIRED* (101).
41 if you for example use --location may cause unintended side-effects when curl
29 any functions that cause signals to be sent to the process. This option is42 effort to never cause such SIGPIPE signals to trigger, but some operating
56 This option may cause libcurl to use the SIGALRM signal to timeout system57 calls on builds not using asynch DNS. In Unix-like systems, this might cause
55 This option may cause libcurl to use the SIGALRM signal to timeout system56 calls on builds not using asynch DNS. In Unix-like systems, this might cause
57 This option may cause libcurl to use the SIGALRM signal to timeout system58 calls on builds not using asynch DNS. In Unix-like systems, this might cause
35 setting this value to something too low might cause unnecessary connection
36 server which might cause the email to be rejected.
44 performance impacts and may cause IPv4 to be used before IPv6 or vice versa.
41 smaller CURLOPT_MAXCONNECTS(3) than before may cause open connections to get
52 (wrong date stamp format might cause the name to not get accepted)
43 *res_init(3)*). This may cause libcurl to keep using the older server even
3 # This case with an unexpected 1xx response used to cause a "hang" before the fix
29 # name resolve will cause it to return rather quickly and thus we could trigger
10 # Crafted to cause error 18
60 Warning: This may cause side-effects. Consider using double quotes?
10 # Crafted to cause error
69 in that memory area. Returning 0 signals end-of-file to the library and cause81 The callback can return *CURL_READFUNC_PAUSE* to cause reading from this90 *CURL_SEEKFUNC_FAIL* to cause the upload operation to fail or
44 transfer is complete might cause libcurl to close the connection - if the
51 lock during that time and it could cause a deadlock.60 silently ignored, outdated log configurations does not cause errors when
37 bad input values may cause libcurl to behave badly. You can only set one
Completed in 35 milliseconds
