Petr Fejfar wrote: >> You need to handle the cookies yourself. That is; you need to store them >> yourself the way you deem suitable. When you "come back" to a site that >> needs a previously saved cookie, you will need to fetch it from the >> place you stored it and provide it to the site. >> >> Handling cookies is not and should not be Synapse's job. Synapse is >> supposed to handle network protocols, not do state management. > > Synapse parses cookies into string list property > THTTPSend.Cookies and its content will be reinstereted > into headers of consecutive HTTP request automatically. > > Hence if your next request goes to a host > the received cookies are related to, > you do not need any extra handling
This requires, I believe, that you use the same instance of the object both times? For me, when working with HTTP, it's usually on the lines of... 1. Create object 2. Use it 3. Free and nil 4. Forget it (next time we start at #1 again) ...which means that after stage 2, I need to store the cookies somewhere and before stage 2 (of the next round) I need to restore them into the object. Of course, if you're just doing a "login, get data, (logout if you wanna do things nicely" from some site, you might very well be using the same object for all queries. -- Markku Uttula ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
