ID: 47701
Updated by: j...@php.net
Reported By: paul at paulmcgarry dot com
Status: Bogus
Bug Type: Unknown/Other Function
Operating System: Linux
PHP Version: 5.2.9
New Comment:
Uh..disregard my previous comment.
This is still bogus. Add your comments to bug #47020 instead of
reporting same thing twice..
Previous Comments:
------------------------------------------------------------------------
[2009-03-21 23:12:32] j...@php.net
FYI: print_f / var_dump are for debugging ONLY..
------------------------------------------------------------------------
[2009-03-21 23:11:32] j...@php.net
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same.
Thank you for your interest in PHP.
------------------------------------------------------------------------
[2009-03-19 01:20:12] fel...@php.net
My mistake, Paul. Sorry.
------------------------------------------------------------------------
[2009-03-18 23:37:10] paul at paulmcgarry dot com
I mentioned 47020 in the first sentence of my initial report so
referring me to it is hardly enlightening or productive and pretty
much indicates you didn't bother to read the report at all (we are
all no doubt time poor, so I understand the temptation!).
If this is bogus then please explain why.
Personally I cannot see how a failure mode that potentially exposes
private data to the user can not be a genuine issue.
------------------------------------------------------------------------
[2009-03-18 23:25:30] fel...@php.net
Please, see bug #47020.
Thanks.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/47701
--
Edit this bug report at http://bugs.php.net/?id=47701&edit=1
