> Subject: Re: cookie and CURLOPT_COOKIEFILE
> On Wed, 17 Sep 2003, Jerry G. Chiuan wrote:
>
> > > But since sending in a zero-length file name works too
>
> > It doesn't work in my case, VC++ pops up "fopen( ) error" could you
please
> > tell me how to specify "empty" file?
>
> By using a file name like "". If this doesn't work, can you please make a
> patch and post it here?

Hi Daniel,
I will try to dig into it

> > I don't want to specify a file which I know not to exist, what if
somebody
> > accidentally creates a file with exactly the same absolute path!
>
> Most systems have path/file names a user can't create.

but this approach is not platform indep.

> > I mean, if we can specify "empty" file for libcurl to "simply turn on
cookie
> > parser" instead of reading from existing cookie file, we don't need to
> > mention "pass file which doesn't exist" for *this purpose*
>
> Well, if an empty file name works for doing this, the existing means still
> work. Thus, I think we should still mention it, but we can of course
change
> the wording in favour of the zero-length file name approach. If that
works.

I agree,
I would mention about "empty" for fetching cookie from response, on the
other hand, "non-empty" file for fetching from existing cookie file

- Jerry

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2003-09-18