Lines Matching refs:url
50 // The base URL should always be canonical, therefore is ASCII.
71 // consistent about URL paths beginning with slashes. This function is like
89 const CHAR* url,
98 url_parse::TrimURL(url, &begin, &url_len);
112 // We treat "C:/foo" as an absolute URL. We can go ahead and treat "/c:/"
117 // shashes should be treated a a relative URL with a hostname.
118 if (url_parse::DoesBeginWindowsDriveSpec(url, begin, url_len) ||
119 url_parse::DoesBeginUNCPath(url, begin, url_len, true))
123 // See if we've got a scheme, if not, we know this is a relative URL.
125 // "http:foo.html" is a relative URL with path "foo.html". If the scheme is
128 if (!url_parse::ExtractScheme(url, url_len, &scheme) || scheme.len == 0) {
141 if (!CanonicalSchemeChar(url[i])) {
149 if (!AreSchemesEqual(base, base_parsed.scheme, url, scheme))
162 int num_slashes = url_parse::CountConsecutiveSlashes(url, colon_offset + 1,
226 // Called on Windows when the base URL is a file URL, this will copy the "C:"
228 // being overridden by the relative URL. Otherwise, do nothing.
250 return base_path_begin; // Relative URL path is "C:/foo"
271 // A subroutine of DoResolveRelativeURL, this resolves the URL knowning that
301 // incoming URL does not provide a drive spec. We save the true path
319 // Since the input should be canonical hierarchical URL, we should
379 // Resolves a relative URL that contains a host. Typically, these will
381 // should be kept from the original URL is the scheme.
390 // Parse the relative URL, just like we would for anything following a
398 // parts of the old URL with the new one.
412 // Resolves a relative URL that happens to be an absolute file path. Examples
420 // Parse the file URL. The file URl parsing function uses the same logic
451 // On error, return the input (resolving a relative URL on a non-relative
460 // Empty relative URL, make no changes.
496 // file: URL only has a host if it has exactly 2 slashes. This also
497 // handles the special case where the URL is only slashes, since that
513 // When we get here, we know that the relative URL is on the same host.
