Thank you. Yes that is a possibility (in addition to saving cookies, disabling the engine to NULL and then reloading the cookies in the engine).
Just a new curl seemed to me a lot of overhead as I do have to connect to the exactly the same url sending me the cookies in the previous connection (cookies I will use again later on). It should be that setting the header as "Cookie;" (the syntax for header cancellation) discards all the auto engine cookies for the next connection, just as "Accept;" discards Accept: */* Thanks! On January 23, 2024 5:35:49 PM GMT+01:00, Daniel Stenberg <dan...@haxx.se> wrote: >On Tue, 23 Jan 2024, Max via curl-library wrote: > >> I have not found in the documentation what is the correct way to disable an >> existing set of cookies (in the cookies engine) temporarily (that means for >> the next single connection where I do not have to send any cookie, including >> persistent ones). > >I think the best way is to create and use a separate easy handle for that >transfer. > >-- > > / daniel.haxx.se > | Commercial curl support up to 24x7 is available! > | Private help, bug fixes, support, ports, new features > | https://curl.se/support.html
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
