docs: document --disable-quic for UDP over SOCKS5

Author: MSTU0

ADVANCED_FEATURES.md

@@ -39,6 +39,7 @@ Smart auto-configuration: timezone, locale, and languages derive from your proxy
 - [Per-context proxies](PER_CONTEXT_FINGERPRINT.md) with proxy-based geo detection (timezone/locale/language) across contexts and sessions
 - DNS-through-proxy plus credentialed proxy URLs keep browser-level geo signals protected
 - UDP-over-SOCKS5 tunnel (ENT Tier3) for QUIC/STUN so ICE presets are only needed when UDP is unavailable
+- Chromium's `--disable-quic` flag remains available for deployments that prefer TCP-based HTTP protocols while keeping SOCKS5 proxying
 - Optional ICE control via [`--bot-webrtc-ice`](CLI_FLAGS.md#behavior--protection-toggles) (ENT Tier1) when the proxy lacks UDP support
 - Chromium-level implementation: tunneling lives inside the network stack, no external proxy-chain hijacking
 

CLI_FLAGS.md

@@ -83,13 +83,22 @@ BotBrowser extends the standard `--proxy-server` flag to accept embedded credent
 
 <a id="udp-over-socks5-ent-tier3"></a>
 ### UDP over SOCKS5 (ENT Tier3)
-ENT Tier3 adds built-in SOCKS5 UDP ASSOCIATE support with no extra flag required. When the proxy supports UDP, BotBrowser will tunnel QUIC traffic and STUN probes over the proxy to harden proxy checks. Guide: [UDP over SOCKS5](https://botbrowser.io/docs/network/udp-over-socks5/)
+ENT Tier3 adds built-in SOCKS5 UDP ASSOCIATE support with no extra flag required. When the proxy supports UDP, BotBrowser will tunnel QUIC traffic and STUN probes over the proxy to keep network identity consistent. Guide: [UDP over SOCKS5](https://botbrowser.io/docs/network/udp-over-socks5/)
 
 ```bash
 # UDP (QUIC/STUN) auto-tunneled when the SOCKS5 proxy supports UDP associate
 --proxy-server=socks5://username:password@proxy.example.com:1080
 ```
 
+To keep SOCKS5 proxying but avoid QUIC/HTTP/3, add Chromium's existing `--disable-quic` flag:
+
+```bash
+--proxy-server=socks5://username:password@proxy.example.com:1080
+--disable-quic
+```
+
+`--disable-quic` affects QUIC/HTTP/3 only. WebRTC/STUN behavior still follows the UDP-over-SOCKS5 and WebRTC settings.
+
 ### `--proxy-ip` (ENT Tier1)
 Specify the proxy's public IP to optimize performance.
 

docs/guides/network/UDP_OVER_SOCKS5.md

@@ -38,6 +38,8 @@ await page.goto("https://example.com");
 await browser.close();
 ```
 
+If your deployment should avoid QUIC/HTTP/3, add Chromium's existing `--disable-quic` flag. The SOCKS5 proxy setting stays the same.
+
 ---
 
 <a id="how-it-works"></a>
@@ -83,6 +85,17 @@ If your proxy supports UDP, everything works automatically:
 
 QUIC and STUN traffic are tunneled through the proxy. TCP traffic is proxied as usual.
 
+### Disable QUIC while keeping SOCKS5
+
+Use Chromium's existing `--disable-quic` flag when you want HTTP traffic to stay on TCP protocols:
+
+```bash
+--proxy-server=socks5://user:pass@proxy.example.com:1080
+--disable-quic
+```
+
+This disables QUIC/HTTP/3. It does not disable WebRTC or STUN; those continue to follow your UDP-over-SOCKS5 and WebRTC settings.
+
 ### When the proxy does not support UDP
 
 If the proxy does not support UDP ASSOCIATE, BotBrowser falls back gracefully:
@@ -124,6 +137,7 @@ const page = await ctx.newPage();
 
 - **Proxy must support UDP ASSOCIATE.** Not all SOCKS5 proxies support UDP. Check with your provider. HTTP and HTTPS proxies do not support UDP tunneling.
 - **Browser-level setting.** UDP proxy support applies at the browser level and cannot be configured per-context independently.
+- **QUIC control.** Use `--disable-quic` when your workload should avoid QUIC/HTTP/3. This does not disable WebRTC.
 - **Performance.** UDP-over-SOCKS5 adds latency compared to direct UDP. For latency-sensitive WebRTC applications, this trade-off favors privacy over raw speed.
 
 ---
@@ -135,6 +149,7 @@ const page = await ctx.newPage();
 | Problem | Solution |
 |---------|----------|
 | QUIC connections not going through proxy | Verify your SOCKS5 proxy supports UDP ASSOCIATE. Not all providers do. |
+| I do not want QUIC traffic | Add `--disable-quic`. SOCKS5 proxying remains active for TCP traffic. |
 | WebRTC still shows real IP | Confirm UDP support. If unavailable, use `--bot-webrtc-ice=google` for ICE control. |
 | Increased latency on some sites | UDP tunneling adds overhead. This is expected. For sites that support both QUIC and HTTP/2, performance should be comparable. |
 | Feature not available | UDP-over-SOCKS5 requires an ENT Tier3 license. |

profiles/PROFILE_CONFIGS.md

@@ -144,7 +144,7 @@ Do not assemble WebKit-family behavior from standalone profile fields. Use the p
 
 ⚠️ **Proxy configurations are intended for authorized networks only. They must not be used for unauthorized data collection or abuse.**
 
-> **[UDP-over-SOCKS5](../CLI_FLAGS.md#udp-over-socks5-ent-tier3):** ENT Tier3 support detects when a SOCKS5 upstream offers UDP associate and natively tunnels QUIC/STUN through it. No additional flag is required; simply provide a SOCKS5 proxy that advertises UDP support.
+> **[UDP-over-SOCKS5](../CLI_FLAGS.md#udp-over-socks5-ent-tier3):** ENT Tier3 support detects when a SOCKS5 upstream offers UDP associate and natively tunnels QUIC/STUN through it. No additional flag is required; simply provide a SOCKS5 proxy that advertises UDP support. Add Chromium's existing `--disable-quic` flag when your workload should avoid QUIC/HTTP/3.
 
 ### HTTP Request Settings