>Why do you think it would be hard to return AUTH_REQUIRED if the
>DEBUG=1 param is in the URL? Granted, the browser issues involved won't
>make it the best solution, but no worse than passwords are already. Someone
>would have to be using a machine where a valid uid/passwd are in browser
cache,
>or someone would have to know a valid uid/password.
>
I like your idea. Yes this should be no problem. How I think I will do it
is to
require a login before presenting the DEBUG submit button. That way it won't
confuse or frustrate the unwary.
>My main worry is how I'm going to produce the best debugging information
>without requiring scripts to be rewritten. As it is, CF displays debugging
>information based on IP. I can mimic the code from cgiwrap to find what I
>would like to send, and I can probably find a way to send the best debugging
>and error reporting to the debugging uid's browser.
Try something like:
if($debug) {
use Data::Dumper;
print "<PRE>";
print "\%list\n";
print Dumper \%$list;
print "</PRE><HR>";
}
