On Tue, 23 Jan 2024, Ray Satiro via curl-library wrote:
You can probably do it with a curl shared object with cookies but you would
have to disable the whole shared object to do it:
Ah yes, clever! I believe that is possible.
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is avai
On 1/23/2024 11:35 AM, Daniel Stenberg via curl-library 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 whe
On Tue, 23 Jan 2024, mab20...@tiscalinet.it wrote:
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: */*
The semicolon version does not really "discard" the he
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 (
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)
Hello.
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).
If I disable the cookie engine setting C
