> At 10:16 +0100 11/15/07, Daniel Stenberg wrote:
>>Right, but since you used LiveHTTPHeaders you should be able to tell if
>> perhaps the site provides a cookie when it presents the form (on a GET),
>> and then assumes you to provide them when you send the POST. Thus, you'd
>> need to do two requests. Lots of sites and servers do this, and the logs
>> will tell you the details.
>
> Note that curl offers its own incoming header viewing with the -D filename
> option. It's possible that the coolies delivered to you using FireFox are
> not really the same as what you get using curl. It's also possible that
> the cookie you should return isn't exactly the same as what is delivered.
> JavaScript can muck with them.
>
> Try the initial GET using curl while saving the headers to a file and see
> what they say.
> --
>
> --> From the U S of A, the only socialist country that refuses to admit
> it. <--
>

Thanks! I'll try all of your suggestions.
Received on 2007-11-15