Skip to content

Data Sources

3. Data Sources (Proxy Sources Tab)

This section is engineered to automate the collection of proxy lists. The primary interface element is a data table featuring the following columns: path, format, proxy type, extract, process type. Each row contains a checkbox for rapidly enabling or disabling that specific source from the synchronization loop. To the right of the table are the management control buttons: Add..., Edit, Delete, View File, Explore to file, Move Up, Move Down, Check All, Uncheck All, Check Selected, Select All, Unselect All.

3.1. Source Parameters (Add Source Dialog)

A source can be configured as either a local file path or a remote URL network asset.

  • File Path/URL: The path pointing to the proxy server source. Adjacent buttons include ... (browse), View (inspects contents inside an internal viewer window), and Explore to file (opens the target directory inside Windows Explorer).
  • Format: Selects one of three standard text-parsing templates (identical to Section 2.4).
  • HTTP Headers: Configures custom request headers (Accept, Referer, User Agent) to bypass remote web server restrictions when fetching lists.
  • SID Tag: An option to enable automated SID generation, containing SID Tag, SID Length, and SID Count parameters.

3.2. Advanced Parsing (Regular Expressions)

To extract proxies from unstructured text payloads or complex HTML source code, regular expression engines are utilized:

  • Extract Pattern: A regular expression (Regex) pattern used to capture the target data block. For example, given the following HTML line: <tr><td class="left"><script>document.write(Base64.decode("MTI3LjAuMC4x"))</script></td><td><span class="fport">1088</span></td></tr>

    The pattern decode\("([^"]+)".+<span class="fport"[^>]+>([0-9]+) will locate the target match: decode("MTI3LjAuMC4x"))</script></td><td style=""><span class="fport" style="">1088, yielding Group 1: MTI3LjAuMC4x and Group 2: 1088.

  • Extract Rule: A structural template to assemble a standardized proxy string using the captured Regex groups ($1, $2, etc.). It supports text literals and built-in conversion string functions:

    1. decode_base64(...) — Decodes Base64-encoded strings.
    2. decode_url(...) — Decodes URL-encoded strings.

    Example Rule: For the payload scenario above, the rule decode_base64($1):$2 transforms the raw input into the standard format: 127.0.0.1:1088.

  • Extract from tag: Narrows down the Regex scanning surface area to a specific HTML tag. It requires a tag name (e.g., tr) and an inspection scope context within it: body (inner text contents) or attribute (value of a specific tag attribute).

  • Extract SID: Allows extracting pre-existing SIDs directly from the raw source content rather than generating them, using an identical set of independent Pattern and Rule parameters.
  • Testing Utilities: The Subject text box is used to paste code fragments manually. The Load button fetches data into it directly from the designated File Path/URL, while the Test button executes a parsing pass to visually verify the correctness of the configured regular expressions.
  • Exclude: Inverts the processing logic of the selected source. When enabled, any proxy found matching these extraction rules will be actively purged from the final verification list.

3.3. Global Source Parameters (Beneath the Table)

  • Append: Appends newly loaded proxy servers to the end of the existing list. If this flag is untoggled, the primary working proxy pool is completely wiped clean before every import cycle.
  • Min. X proxies in source: A fail-safe threshold barrier. If a source yields fewer than X proxies (e.g., a remote website encounters an error), the application ignores the update and preserves the existing working proxy pool, preventing operational failures in connected downstream software.
  • Save all loaded proxies to file: Duplicates all collected raw, unverified proxies into a unified single file for subsequent external analysis.