in reply to Re^2: Cookie->fetch problem
in thread Cookie->fetch problem

OK. Then here's what you can do:
1) Fix your original post's formatting (ie: add <p> tags). See Markup in the Monastery
2) Add use Data::Dumper; at the top of your file, and turn warn %cookies; into warn Dumper \%cookies;, you'll get a clearer view of what fetch() returns.

Replies are listed 'Best First'.
Re^4: Cookie->fetch problem
by tultalk (Monk) on Mar 09, 2017 at 17:06 UTC

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

    Where does data dumper dump data?

    As a side issue, I looked at cookies in the firefox options and it showed three on my main page including the CGISESSID

    I then looked at the cookies with the Firebug cookie panel and there were only two and unrecognizable in relation to the Firefox Options cookie viewer. Is there something obvious zi am missing?

    Thanks

[reply]
      A review of Basic debugging checklist may be helpful.

      #11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.

[reply]
      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

[reply]

        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]

        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]

In Section Seekers of Perl Wisdom