URL (Uniform Resource Locator)

Examine the complete structural breakdown of an RFC 3986 URL: ``` https://user:pass@api.toolqix.store:443/v1/tools/search?q=pdf&sort=asc#results \___/ \_______/ \______________/ \_/ \____________/ \___________/ \______/ Scheme UserInfo Hostname Port Path Query Fragment (Proto) \______________________________/ Authority ``` 1. Scheme / Protocol: Specifies how data is transferred (`https`, `http`, `ftp`, `mailto`, `ssh`). 2. Authority: Composed of optional UserInfo (`user:pass@`), the registered Hostname or IP address (`api.toolqix.store`), and optional Port number (`:443`). 3. Path: Hierarchical directory routing path identifying the resource on the host (`/v1/tools/search`). 4. Query String: Key-value parameters prefixed with `?` and separated by `&` (`?q=pdf&sort=asc`). 5. Fragment / Hash: Anchor prefixed with `#` identifying a specific element within the document. Sent only to the client browser—never transmitted over HTTP requests to the server.

Clarifying the relationship between web identification standards:

Using the modern browser and Node.js WHATWG URL API for safe URL construction:

export function parseAndCleanUrl(rawUrl: string): {
  valid: boolean;
  hostname?: string;
  pathname?: string;
  queryParams?: Record<string, string>;
} {
  try {
    const parsed = new URL(rawUrl);
    const queryParams: Record<string, string> = {};
    parsed.searchParams.forEach((val, key) => {
      queryParams[key] = val;
    });

    return {
      valid: true,
      hostname: parsed.hostname,
      pathname: parsed.pathname,
      queryParams
    };
  } catch {
    return { valid: false };
  }
}