Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Cached CURL handle causing problems with PUT Data?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: kent williams via curl-library <curl-library_at_cool.haxx.se>
Date: Tue, 20 Apr 2021 14:08:04 -0500
Ran into this.
I implemented using the same CURL handle across separate HTTP requests,
but it appears to screw things up in the case where I use it after a
PUT, if I've used CURLOPT_READDATA and CURLOPT_READFUNCTION.
How do I reset those options so that a subsequent GET request doesn't
try and use that put data?
Also if I set CURLOPT_CUSTOMREQUEST, how do I reset it?
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-04-20
Date: Tue, 20 Apr 2021 14:08:04 -0500
Ran into this.
I implemented using the same CURL handle across separate HTTP requests,
but it appears to screw things up in the case where I use it after a
PUT, if I've used CURLOPT_READDATA and CURLOPT_READFUNCTION.
How do I reset those options so that a subsequent GET request doesn't
try and use that put data?
Also if I set CURLOPT_CUSTOMREQUEST, how do I reset it?
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-04-20