CURL Transport sometimes reports failures accessing https://twitter.com in MultipleCrlOperationsTest

[LarryOsterman]

Describe the bug
Several failures have been observed in the CI pipeline running the Validate Win2019_Win32Api_curl_x86 step.

The test failure I'm seeing mostly is a failure in curl.cpp:

  if (data != expected)
  {
    throw TransportException(
        "Unexpected format in HTTP response. Expecting: " + std::to_string(expected)
        + ", but found: " + std::to_string(data) + ".");
  }

The assert is reporting that instead of the expected \13 the server is sending \34 ("). This comes from CurlSession::ReadCRLF which is expecting a \r\n sequence.

[github-actions]

Hi @LarryOsterman, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.