Searched refs:follow (Results 1 – 25 of 38) sorted by relevance
12
21 CURLOPT_FOLLOWLOCATION - follow HTTP 3xx redirects33 A long parameter set to 1 tells the library to follow any Location: header35 can specify a relative or an absolute URL to follow.42 libcurl restricts what protocols it automatically follow redirects to. The54 follow logic with the use of curl_easy_getinfo(3)'s CURLINFO_REDIRECT_URL(3)65 protection from this happening when libcurl is told to follow redirects.90 /* example.com is redirected, so we tell libcurl to follow redirection */
35 In cases when you have asked libcurl to follow redirects, the method may not be
32 In cases when you have asked libcurl to follow redirects, it may not be the same
59 /* follow redirects */
33 channel communication remains unencrypted. This allows NAT routers to follow
46 For RTSP, the formatting of a range should follow RFC 2326 Section 12.29. For
35 follow a redirect it makes matching cookies get sent accordingly.
57 protection from this happening when libcurl is told to follow redirects.
59 right bracket and matches exactly one character. Some examples follow:
196 /* example.com is redirected, so we tell libcurl to follow redirection */
76 and follow the login and password that are associated with that machine.
19 Set maximum number of redirections to follow. When --location is used, to
21 unencrypted. This allows NAT routers to follow the FTP transaction. The
21 slash or other data that does not follow the regular URL pattern, like
19 Instructs curl to like --location follow HTTP redirects, but permits it to
30 Limit the amount of redirects to follow by using the --max-redirs option.
3 # when the URI contains 2 '#' (does not follow RFC 2396)
43 HTTP follow redirect with single slash in path
49 HTTP follow redirect with excessive ../
49 HTTP follow redirect with ../
49 HTTP follow redirect with ../../
49 HTTP follow redirect with ./-prefix
59 HTTP follow redirect from IPv4 to IPv6 with scope
100 HTTP with NTLM and follow-location
138 HTTP with NTLM via --anyauth, and then follow-location with NTLM again
Completed in 24 milliseconds
