Lines Matching full:urls
117 user running the libcurl application, SCP: or SFTP: URLs could access password
130 \fICURLOPT_FOLLOWLOCATION(3)\fP and handling redirects itself, sanitizing URLs
144 All the malicious scenarios regarding redirected URLs apply just as well to
145 non-redirected URLs, if the user is allowed to specify an arbitrary URL that
206 .SH "Dangerous SCP URLs"
207 SCP URLs can contain raw commands within the scp: URL, which is a side effect
212 Applications must not allow unsanitized SCP: URLs to be passed in for
215 By default curl and libcurl support file:// URLs. Such a URL is always an
217 avoid that, keep control of what URLs to use and/or prevent curl/libcurl from
220 By default, libcurl prohibits redirects to file:// URLs.
247 curl supports URLs mostly according to how they are defined in RFC 3986, and
252 This deviance makes some URLs copied between browsers (or returned over HTTP
337 passwords, things like URLs, cookies or even file names could also hold