Re^5: Cookie->fetch problem

I did use the tags on the text. I guess you mean at every paragraph etc.

I mean that your post is hard to read because of the bad formatting. You'll be more likely to obtain an answer if people don't have to guess where the linebreaks are supposed to be.

Where does data dumper dump data?

It turns it into a string, actually valid perl code that compiles back into the dumped data. This means you get to see exactly what your data is. In your case, you'll see that wherever you look to see the output from warn

Comment on Re^5: Cookie->fetch problem

Replies are listed 'Best First'.
Re^6: Cookie->fetch problem by tultalk (Monk) on Mar 09, 2017 at 18:43 UTC
Hi Never seen something like this in the error log before. Thu Mar 9 12:33:53 2017 manage_users.cgi: $VAR1 = {}; Is that from data dumper?	[reply]
Re^7: Cookie->fetch problem by kennethk (Abbot) on Mar 09, 2017 at 19:00 UTC
That is the output from Data::Dumper. You can see the cookies hash (aliased here to `$VAR1`) is empty. Otherwise, it might output something like: `[Thu Mar 9 12:33:53 2017] manage_users.cgi: $VAR1 = {'CGISESSID' => '1 +234deadbeef'};` [download] For a quasi-independent test, what happens when you add the following to your code: `use CGI; my $cgi = CGI->new; warn $_ for $q->cookie();` [download] and see if the CGI object has any cookies in it. #11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.	[reply] [d/l] [select]
Re^6: Cookie->fetch problem by tultalk (Monk) on Mar 09, 2017 at 18:30 UTC
Perhaps I am dense. It turns it into a string, actually valid perl code that compiles back into the dumped data. Where do I see the dumped data?	[reply]