From 713cc909c7ae0c6ee5ba9b2a5b8e8b1a0a6d30a8 Mon Sep 17 00:00:00 2001
From: thePR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com>
Date: Wed, 24 Sep 2025 16:22:02 -0400
Subject: [PATCH] Document probeUrl HEAD and range fallback

---
 js/app.js | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/js/app.js b/js/app.js
index 5ef902c3..a1fb40ff 100644
--- a/js/app.js
+++ b/js/app.js
@@ -2118,6 +2118,13 @@ class bitvidApp {
     }
   }
 
+  /**
+   * HEAD first avoids downloading bytes when probing, but many hosts reject
+   * HEAD or omit `Accept-Ranges`, so we fall back to a tiny `Range:
+   * bytes=0-1023` GET and only warn when range headers are missing. This
+   * fallback prevents false "unplayable" results and should stay paired with
+   * the HEAD logic unless a new probe keeps both paths in sync.
+   */
   async probeUrl(url) {
     const trimmed = typeof url === "string" ? url.trim() : "";
     if (!trimmed) {