Windows + Edge 环境使用反馈: 代理稳定性 / API 功能补充 / 路径兼容性
作者: liulinxi607创建于 2026年6月10日更新于 2026年6月21日
- CDP Proxy connection stability problems: 1.1 Process mutual exclusion: pkill -f cdp-proxy.mjs is invalid in Windows bash, and the old process continues to occupy port 3456. 1.2 Unable to recover after disconnection: After the browser WebSocket is disconnected, the proxy repeatedly reconnects and all connections fail. 1.3 --browser must be passed each time: The configuration environment preferences are not properly persisted, and they need to be specified again each time. 2. API functionality deficiencies: 2.1 Lack of printToPDF endpoint: CDP Page.printToPDF is the most reliable way to obtain the entire page (full page, text optional, small file size). The current proxy does not expose it. 2.2 Screenshot does not support full page: / screenshot does not support captureBeyondViewport. Large pages only capture the viewport. When the clip + full page parameter is used, it directly times out (1280 × 4334px, etc. 90s +). 2.3 CDP command timeout is hard-coded: sendCDP timeout is 30000ms and cannot be customized. Slow operations such as printToPDF / full-page screenshot are not enough. 3. Path compatibility: bash / tmp and Node.js / tmp resolve to different directories (C:/Users/alin/AppData/Local/Temp vs C:/tmp), and the files are not visible to each other. 4. Summary: The above problems lead to the fact that it is more reliable to bypass the proxy and directly connect to the CDP WebSocket in actual operations. The proxy direction is good, and we hope it will be more stable.
内容来源: eze-is/web-access