Bug 257705 – [Curl] Proxy authentication during CONNECT request is not working after 256639@main.

• Status: RESOLVED
• Resolution: FIXED
• Component: Platform

[Kenji Shukuwa]

Proxy authentication does not work after 256639@main. 

If CURLINFO_HTTP_CONNECTCODE is 407, invokeDidReceiveResponse() should be called to handle
proxy authentication (NetworkDataTaskCurl::tryProxyAuthentication).

---
CurlRequest::didCompleteTransfer() ==>
CurlRequest::invokeDidReceiveResponse() ==>
NetworkDataTaskCurl::curlDidReceiveResponse() ==>
NetworkDataTaskCurl::tryProxyAuthentication()
---

[Kenji Shukuwa]

Pull request: https://github.com/WebKit/WebKit/pull/14664

[Kenji Shukuwa]

Comment 0 was not an accurate description. Correctly, proxy authentication for CONNECT requests is no longer working.

If you get a proxy authentication (407) response after sending a CONNECT request to the proxy server, Proxy authentication processing was performed before 256639@main, but an error occurs after 256639@main.

Major browsers handle proxy authentication responses to CONNECT requests. So, fix it so that the curl port can also perform proxy authentication.

[EWS]

Committed 264874@main (be820d76b164): <https://commits.webkit.org/264874@main>

Reviewed commits have been landed. Closing PR #14664 and removing active labels.

[Radar WebKit Bug Importer]

<rdar://problem/110275130>

[Fujii Hironori]

Playwright issue: https://github.com/microsoft/playwright/issues/22184