From 19b84e09b9a1faae6c3a5b87c8917cf64f6b3b81 Mon Sep 17 00:00:00 2001
From: TwistedFate <17706267+CEastWind@users.noreply.github.com>
Date: Tue, 7 Jul 2026 00:27:55 +0800
Subject: [PATCH] =?UTF-8?q?fix(captcha):=20personal=20=E6=A8=A1=E5=BC=8F?=
 =?UTF-8?q?=E8=AE=A4=E8=AF=81=E4=BB=A3=E7=90=86=E9=80=8F=E4=BC=A0=E7=BB=99?=
 =?UTF-8?q?=20Flow=20=E8=AF=B7=E6=B1=82=EF=BC=8C=E4=BF=AE=E5=A4=8D?=
 =?UTF-8?q?=E4=B8=8A=E4=BC=A0/=E7=94=9F=E6=88=90=20=E4=BB=A3=E7=90=86?=
 =?UTF-8?q?=E8=AE=A4=E8=AF=81=E4=BF=A1=E6=81=AF=E4=B8=A2=E5=A4=B1?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

personal 模式下 _resolve_personal_proxy 解析出带 user:pass 的代理后，
self._proxy_url 被存成剥离账密的 {protocol}://{host}:{port}（本意是给 Chrome
--proxy-server / 认证扩展用，Chrome 不吃 URL 里的账密）。但该值同时被复用为
Flow API 请求(curl_cffi)的出口代理，导致带认证代理下 /flow/uploadImage 等
请求丢失代理认证信息、上传首尾帧失败、视频无法生成。

改为用 _compose_proxy_url 组装带账密的完整地址存入 self._proxy_url。Chrome 侧
代理认证走扩展/命令行 proxy_server_arg，不依赖该值，打码浏览器不受影响；仅补齐
了 Flow 请求侧的代理认证。
---
 src/services/browser_captcha_personal.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/services/browser_captcha_personal.py b/src/services/browser_captcha_personal.py
index 5d70f65b..eecc6190 100644
--- a/src/services/browser_captcha_personal.py
+++ b/src/services/browser_captcha_personal.py
@@ -9287,7 +9287,8 @@ async def initialize(self):
                             )
                         else:
                             proxy_server_arg = f"--proxy-server={protocol}://{host}:{port}"
-                        self._proxy_url = f"{protocol}://{host}:{port}"
+                        # Flow API 请求(curl_cffi)复用此值，必须带 user:pass，否则认证代理会 407
+                        self._proxy_url = _compose_proxy_url(protocol, host, port, username, password)
                         debug_logger.log_info(f"[BrowserCaptcha] Personal 浏览器代理: {self._proxy_url}")
 
                     browser_args = _build_personal_browser_args(