You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I compared the use with the requests library. While also using the get method to initiate a request with a request body, the curl_cffi library actually initiates a post request。The code is as follows:
Additional context
The server is a simple server written using golang's gin. In addition to that, get requests sent to me locally using curl_cffi are not captured by fiddler, but requests sent to me locally by the requests library are captured by fiddler.
The text was updated successfully, but these errors were encountered:
I found that if I add a proxy to the curl_cffi request and set the value to the port that fiddler listens on, fiddler captures the curl_cffi request correctly. But why does the requests library not need to be configured with a proxy for fiddler to capture the request correctly?
Describe the bug
I compared the use with the requests library. While also using the get method to initiate a request with a request body, the curl_cffi library actually initiates a post request。The code is as follows:
Versions
Additional context
The server is a simple server written using golang's gin. In addition to that, get requests sent to me locally using curl_cffi are not captured by fiddler, but requests sent to me locally by the requests library are captured by fiddler.
The text was updated successfully, but these errors were encountered: