Workflow 的 WFHttpTask 是否支持浏览器 TLS 指纹模拟

During the WFHttpTask web page crawling process, some websites identify the client based on TLS fingerprints (such as JA3). Currently, the default TLS behavior of Workflow based on OpenSSL differs significantly from that of mainstream browsers such as Chrome and Firefox, and in some strictly anti-crawling scenarios, requests are easily identified as non-browser traffic, resulting in failed crawling. At present, WFHttpTask of Workflow encapsulates the underlying socket + TLS logic, but the TLS fingerprint (ClientHello, including cipher suites, extensions, ALPN, etc.) is not configurable and cannot directly simulate the behavior of mainstream browsers. The existing set_ssl_ctx interface is mainly used for certificate verification and other configurations, and cannot adjust the handshake details.