Daniel Stenberg wrote:

>In case this is where you're using the previously stored cookies
>I think it makes sense.
>
>Paul Harrington and I sorted out a bug in the cookie parser
>that could be it. It would be very interesting to see the contents
>of that cookie file, as well as it would be intereting to know
>where in the code it crashed...

The file was blank.. from what i understood from the curl man page, if you
specified a string without an '=' with the -b option, it would either read
from or write to the filename specified depending on the action needed (me
reciving a cookie, or the server requesting one back).. hopfully this is
correct..

but anyways.. more specificly, this is what i was hopeing to do with curl.
1) connect to a https server and POST some data to it... in return the
server would send me a cookie with a session id number, and anohter cookie
storing one of the fields in the POST i did.. 2) reconnect to the same https
server and POST some more data to it.. but now each time i connect, the
server will request the session id cookie, and the other coookie...

i was able to use curl with the -b option if i manualy entered in the
cookie's that i needed to send to the server.. but.. that kinda wrecks the
idea of automating the task if i have to do it manualy..

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
Received on 2000-02-22