Greasy Fork is available in English.

pURLfy

The ultimate URL purifier

当前为 2024-04-09 提交的版本，查看最新版本。

此脚本不应直接安装。它是供其他脚本使用的外部库，要使用该库请加入元指令 // @require https://update.greasyfork.icu/scripts/492078/1357329/pURLfy.js

提问、发表评价或者举报此脚本。

作者: PRO-2684
版本: 0.0.1.20240409144441
创建于: 2024-04-09
更新于: 2024-04-09
大小: 8.9 KB
许可证: 暂无

pURLfy

English | 简体中文

The ultimate URL purifier.

[!NOTE] Do you know that the name "pURLfy" is a combination of "purify" and "URL"? It can be pronounced as pjuɑrelfaɪ.

🪄 Functionalities

Purify URL: Remove redundant tracking parameters, skip redirecting pages, and extract the link that really matters.

⚡ Fast: Purify URLs quickly and efficiently. (Time complexity is $O(n)$, where $n$ is the count of / in the URL path.)
🪶 Lightweight: Zero-dependency; The minified script is only 2.1kb.
📃 Rule-based: Perform purification based on rules, making it more flexible.
🔁 Iterative purification: If the URL still contains tracking parameters after a single purification (e.g. URLs returned by redirect rules), it will continue to be purified.
📊 Statistics: You can track statistics of the purification process, including the number of links purified, the number of parameters removed, the number of URLs decoded, the number of URLs redirected, and the number of characters deleted, etc.

🤔 Usage

🚀 Quick Start

// Somewhat import `Purlfy` class from https://cdn.jsdelivr.net/gh/PRO-2684/pURLfy@latest/purlfy.min.js
const purifier = new Purlfy({ // Instantiate a Purlfy object
    redirectEnabled: true,
    lambdaEnabled: true,
});
const rules = await (await fetch("https://cdn.jsdelivr.net/gh/PRO-2684/pURLfy@latest/rules/<country>.json")).json(); // Rules
purifier.importRules(rules); // Import rules
const additionalRules = {}; // You can also add your own rules
purifier.importRules(additionalRules);
purifier.addEventListener("statisticschange", e => { // Add an event listener for statistics change
    console.log("Statistics changed to:", e.detail);
});
purifier.purify("https://example.com/?utm_source=123").then(console.log); // Purify a URL

📚 API

Constructor

new Purlfy({
    redirectEnabled: Boolean, // Enable the redirect mode (default: false)
    lambdaEnabled: Boolean, // Enable the lambda mode (default: false)
    maxIterations: Number, // Maximum number of iterations (default: 5)
    statistics: { // Initial statistics
        url: Number, // Number of links purified
        param: Number, // Number of parameters removed
        decoded: Number, // Number of URLs decoded (`param` mode)
        redirected: Number, // Number of URLs redirected (`redirect` mode)
        char: Number, // Number of characters deleted
    },
    log: Function, // Log function (default: `console.log.bind(console, "\x1b[38;2;220;20;60m[pURLfy]\x1b[0m")`)
})

Methods

importRules(rules: object): void: Import rules.
purify(url: string): Promise<object>: Purify a URL.
- url: The URL to be purified.
- Returns a Promise that resolves to an object containing:
  - url: string: The purified URL.
  - rule: string: The matched rule.
clearStatistics(): void: Clear statistics.
clearRules(): void: Clear all imported rules.
getStatistics(): object: Get statistics.
addEventListener("statisticschange", callback: function): void: Add an event listener for statistics change.
- The callback function will receive an Event object with the detail property containing the new statistics. (detail might not work on nodejs - call getStatistics)
removeEventListener("statisticschange", callback: function): void: Remove an event listener for statistics change.

Properties

You can change these properties after instantiation, and they will take effect for the next call to purify.

redirectEnabled: Boolean: Whether the redirect mode is enabled.
lambdaEnabled: Boolean: Whether the lambda mode is enabled.
maxIterations: Number: Maximum number of iterations.

📖 Rules

The format of the rules rules is as follows:

{
    "<domain>": {
        "<path>": {
            // A single rule
            "description": "<规则描述>",
            "mode": "<模式>",
            // Other parameters
            "author": "<作者>"
        },
        // ...
    },
    // ...
}

✅ Path Matching

<domain>, <path>: The domain and a part of path, such as example.com/, path/ and page (Note that the leading / is removed). Here's an explanation of them:

The basic behavior is like paths on Unix file systems.
- If not ending with /, its value will be treated as a rule.
- If ending with /, there's more paths under it, like "folders" (theoretically, you can nest infinitely)
- / is not allowed in the middle of <domain> or <path>.
If it's an empty string "", it will be treated as a FallBack rule: this rule will be used when no other rules are matched at this level.
If there's multiple rules matched, the rule with the longest matched path will be used.
If you want a rule to match all paths under a domain, you can omit <path>, but remember to remove the / after the domain.

A simple example with comments showing the URLs that can be matched:

{
    "example.com/": {
        "a": {
            // The rule here will match "example.com/a"
        },
        "path/": {
            "to/": {
                "page": {
                    // The rule here will match "example.com/path/to/page"
                },
                "": {
                    // The rule here will match "example.com/path/to", excluding "page" under it
                }
            },
            "": {
                // The rule here will match "example.com/path", excluding "to" under it
            }
        },
        "": {
            // The rule here will match "example.com", excluding "path" under it
        }
    },
    "example.org": {
        // The rule here will match every path under "example.org"
    },
    "": {
        // Fallback: this rule will be used for all paths that are not matched
    }
}

Here's an erroneous example:

{
    "example.com/": {
        "path/": { // Path ending with `/` will be treated as a "directory", thus you should remove the trailing `/`
            // Attempting to match "example.com/path"
        }
    },
    "example.org": { // Path not ending with `/` will be treated as a rule, thus you should add a trailing `/`
        "page": {
            // Attempting to match "example.org/page"
        }
    },
    "example.net/": {
        "path/to/page": { // Can't contain `/` in the middle - you should nest them
            // Attempting to match "example.net/path/to/page"
        }
    }
}

📃 A Single Rule

Paths not ending with / will be treated as a single rule, and there's multiple modes for a rule. The common parameters are as follows:

{
    "description": "<Rule Description>",
    "mode": "<Mode>",
    // Mode-specific parameters
    "author": "<Author>"
}

This table shows supported parameters for each mode:

Param\Mode	`white`	`black`	`param`	~~`regex`~~	`redirect`	`lambda`
`params`	✅	✅	✅	❓	❌	❌
`decode`	❌	❌	✅	❓	❌	❌
`lambda`	❌	❌	❌	❓	❌	✅
`continue`	❌	❌	✅	❓	✅	✅

🟢 Whitelist Mode `white`

Param	Type	Default
`params`	`string[]`	Required

Under Whitelist mode, only the parameters specified in params will be kept, and others will be removed. Usually this is the most commonly used mode.

🟠 Blacklist Mode `black`

Param	Type	Default
`params`	`string[]`	Required

Under Blacklist mode, the parameters specified in params will be removed, and others will be kept.

🟤 Specific Parameter Mode `param`

Param	Type	Default
`params`	`string[]`	Required
`decode`	`string[]`	`["url"]`
`continue`	`Boolean`	`true`

Under Specific Parameter mode, pURLfy will:

Attempt to extract the parameters specified in params in order, until the first existing parameter is matched.
Decode the parameter value using the decoding functions specified in the decode array in order (if the decode value is invalid, this decoding function will be skipped).
Use the final result as the new URL.
If continue is not set to false, purify the new URL again.

Currently supported decode functions are:

url: URL decoding (decodeURIComponent)
base64: Base64 decoding (decodeURIComponent(escape(atob(s))))

🟣 Regex Mode `regex`

TODO

🟡 Redirect Mode `redirect`

[!CAUTION] For compatibility reasons, the redirect mode is disabled by default. Refer to the API documentation for enabling it.

Param	Type	Default
`continue`	`Boolean`	`true`

Under Redirect mode, pURLfy will:

Attempt to fire a HEAD request to the matched URL.
If the status code is 3xx, the Location header will be used as the new URL.
If continue is not set to false, purify the new URL again.

🔵 Lambda Mode `lambda`

[!CAUTION] For security reasons, the lambda mode is disabled by default. Refer to the API documentation for enabling it.

Param	Type	Default
`lambda`	`string`	Required
`continue`	`Boolean`	`true`

Under Lambda mode, pURLfy will try to execute the lambda function specified in lambda and use the result as the new URL. The function body should accept a single URL parameter url and return a new URL object. For example:

{
    "example.com": {
        "description": "示例",
        "mode": "lambda",
        "lambda": "url.searchParams.delete('key'); return url;",
        "continue": false,
        "author": "PRO-2684"
    },
    // ...
}

If URL https://example.com/?key=123 matches this rule, the key parameter will be deleted. After this operation, since continue is set to false, the URL returned by the function will not be purified again. Of course, this is not a good example, because this can be achieved by using Blacklist mode.

pURLfy

🪄 Functionalities

🤔 Usage

🚀 Quick Start

📚 API

Constructor

Methods

Properties

📖 Rules

✅ Path Matching

📃 A Single Rule

🟢 Whitelist Mode white

🟠 Blacklist Mode black

🟤 Specific Parameter Mode param

🟣 Regex Mode regex

🟡 Redirect Mode redirect

🔵 Lambda Mode lambda

🟢 Whitelist Mode `white`

🟠 Blacklist Mode `black`

🟤 Specific Parameter Mode `param`

🟣 Regex Mode `regex`

🟡 Redirect Mode `redirect`

🔵 Lambda Mode `lambda`