Skip to main content

Upload and extract function

Allows you to send a file to a file host, extract the download link and, if required, manage the manual deletion of the file.

🧠 Function overview​

function upload_to_host(request_data, response_format, link_extraction = [], affix = [], manage_file = []) {
  // ...
}

📦 Parameters explained​

📍 request_data​

The base configuration for the HTTP request to the host:

  • request_data[0] → Endpoint URL
  • request_data[1] → HTTP method ("POST", "GET"…)
  • request_data[2] → Body of the request (e.g. a FormData object)
  • request_data[3] → Optional headers (e.g. { "Content-Type": "application/json" })

📬 response_format​

Type of response expected from the server:

  • "json" → if the server returns a JSON object
  • "text" → if the server returns plain text or HTML

🔗 link_extraction​

Rules to extract the download link from the server’s response:

  • 🔹 Static: ["https://example.com/" + code] — build the link manually
  • 🔹 Regex match: ["match", /regex/, index] — extract using a rege
  • 🔹 Replace: ["replace", "&", "_"] — replace characters in a string
  • 🔹 JSON path: ["data", "downloadPage"] → will return data["data"]["downloadPage"]

🧩 affix​

Used to wrap the final link with a prefix and/or suffix:

  • affix[0] → prefix (e.g. "https://host.com/file/")
  • affix[1] → suffix (e.g. ".html")

🗑️ manage_file​

Used for hosts that allow deleting the uploaded file:

  • manage_file[0] → Delete URL (string, regex, or nested JSON path)
  • manage_file[1] → HTTP method ("DELETE", "POST"...)
  • manage_file[2] → Delete body content
  • manage_file[3] → [prefix, suffix] for delete URL

🧨 Special Case: Killcode System​

Some hosts (like those using XFileSharing Pro) require an extra step with a killcode before deletion. This is handled automatically:

if (manage_file[2][key][0] === "killcode") {
  // Logic to extract the file ID
  // Fetch the killcode page
  // Extract killcode and optional token, code or/and rand
}

This allows deletion for hosts that use:

  • Separate token-based deletion pages
  • CSRF-protected forms
  • Dynamic or time-based kill links

🧪 Examples​

✅ Example 1: JSON + Direct link​

upload_to_host(
  [
    "https://example.com/upload", 
    "POST", 
    formData, 
    { Authorization: "Bearer token" }
  ],
  "json",
  ["data", "url"]
);

✅ Example 2: Text + Regex match​

upload_to_host(
  [
    "https://example.com/upload", 
    "POST", 
    formData
  ],
  "text",
  ["match", /https:\/\/example\.com\/file\/[a-z0-9]+/, 0]
);

✅ Example 3: Real case (Gofile)​

const sent_data_form = new FormData();
sent_data_form.append("file", STATE.file_to_upload);

const headers = api_key_host ? { "Authorization": "Bearer " + api_key_host } : {};

upload_to_host(
  [
    URL_FOR_BYPASS_CORS + "https://upload.gofile.io/uploadfile",
    "POST",
    sent_data_form,
    headers
  ],
  "json",
  ["data", "downloadPage"],
  [],
  api_key_host
  ? [
      "https://api.gofile.io/contents",
      "DELETE",
      {
        "contentsId": ["data", "parentFolder"]
      },
      [],
      headers
    ]
  : [
      "https://api.gofile.io/contents",
      "DELETE",
      {
        "contentsId":["data", "parentFolder"], "token": ["data", "guestToken"]
      }
    ]
);