I don't know exactly how the cookie is written on client, but of
course if cURL dosen't support javascript, it could be the reason.
It could'nt the second one, because, I interogatea single frame web page.

2005/12/9, Ralph Mitchell <ralphmitchell_at_gmail.com>:
> You need to check what the server returns. There is probably some
> javascript that set/gets a cookie, and curl doesn't do javascript...
> If that's the case, you have to work out what it does and mimic it in
> your script.
>
> Are you following the whole chain of pages?? Jumping into the middle
> of a web site can mean you miss out on a cookie exchange that happens
> with an earlier page. One time I was trying to grab pages from a
> server that was handing out a different cookie with each frame of the
> page. I had to get every single stinking frame, in the correct
> sequence, before it would let me have the frame I actually wanted...
>
> Ralph Mitchell
>
>
> On 12/9/05, Cyril <cyrilguillot_at_gmail.com> wrote:
> > Hi everybody,
> >
> > when I interrogate a server with generate a "session cookie", with a
> > cURL inline command, I obtain a message that says my browser doesn't
> > support cookies.
> >
> > I don't undestand this message because I don't use a browser but cURL.
> >
> > What I understand is that cURL doesn't support cookie.
> > So I try to use -c or/and -b option but with the same result.
> >
> > The manual says that -c option is to tell in wich file the server
> > write cookies and -b to tell in which file the server read cookies,
> > right?
> >
> > Has anybody already have this problem?
> > Somebody can tell me how to interrogate this server?
> >
> > Thank's a lot.
> > Cyril.
> >
> >
>
>
Received on 2005-12-09