Hi Meir. On 2011/08/06 23:53, Meir Guttman wrote: > The point with cookies, at least in my applications, is that I always have > to return to the server the cookie I got in the first "GET" with a > base/default url. > > So all you have to do is to provide a CONTAINER in which Mech/LWP deposits > the cookie it gets in a response. Its contents is then used when these > packages send another GET (or a POST?) out. You don't EXPLICITLY send > anything; no more then you send all the other parameters in the HTTP HEADER > such as 'User-Agent', 'Accept-Encoding', etc. You just set these up in the > object and the package uses them as it see fit. This is your use case, my use case is different. We are in the process of security review, after an incident of one of our clients was hacked. so after that specific security hole was patched, we are trying to find other problems with our CMS. so I'm now wearing my hacker hat, and cooking malicious cookies and requests to demo problems that I find in the code. so in my use case, the website won't supply these cookies. I need to explicitly create them.
Shmuel. _______________________________________________ Perl mailing list [email protected] http://mail.perl.org.il/mailman/listinfo/perl
