Lines Matching full:urls

118 user running the libcurl application, SCP: or SFTP: URLs could access password
131 CURLOPT_FOLLOWLOCATION(3) and handling redirects itself, sanitizing URLs
160 All the malicious scenarios regarding redirected URLs apply just as well to
161 non-redirected URLs, if the user is allowed to specify an arbitrary URL that
186 based on numerical IPv4 addresses used in URLs. This is a bad and error-prone
239 # Dangerous SCP URLs
241 SCP URLs can contain raw commands within the scp: URL, which is a side effect
246 Applications must not allow unsanitized SCP: URLs to be passed in for
251 By default curl and libcurl support file:// URLs. Such a URL is always an
253 avoid that, keep control of what URLs to use and/or prevent curl/libcurl from
256 By default, libcurl prohibits redirects to file:// URLs.
320 curl supports URLs mostly according to how they are defined in RFC 3986, and
325 This deviance makes some URLs copied between browsers (or returned over HTTP
327 an application parses URLs differently from libcurl and makes different
332 curl_url(3) API to parse URLs, ensuring that they are parsed the same way
423 passwords, things like URLs, cookies or even file names could also hold