Skip Menu |

This queue is for tickets about the CGI-Application-Plugin-DevPopup CPAN distribution.

Report information
The Basics
Id: 42315
Status: resolved
Priority: 0/
Queue: CGI-Application-Plugin-DevPopup

People
Owner: rhesa [...] cpan.org
Requestors: COSMICNET [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: (no value)
Fixed in: (no value)



Subject: DevPopup/HTTPHeaders.pm warnings cause issues on IIS7
DevPopup/HTTPHeaders.pm is spitting out warnings that can cause problems if ran through IIS. The warnings are:- Use of uninitialized value $parameter in pattern match (m//) at (eval 28) line 3. Use of uninitialized value in transliteration (tr///) at (eval 28) line 4. Use of uninitialized value in join or string at C:/inetpub/wwwroot/cgi-bin/affiliate/cpanlib/CGI/Application/Plugin/DevPopup/HTTPHeaders.pm line 73. IIS has a nasty habbit of sending messages aim at STDERR to STDOUT instead, which ends up putting these warnings in your cgi's output heading, which causes a "HTTP Error 502.2 - Bad Gateway" on IIS7 which is very strict on the headers it receives. IIS5.1 and 6 aren't as fussy, although you may experience other problems. It would be ideal if these warnings could be surpressed. A code around is to close STDERR as the start of your script. BEGIN { close(STDERR); } Lyle
Hi Lyle, On Sun Jan 11 20:19:16 2009, COSMICNET wrote: Show quoted text
> DevPopup/HTTPHeaders.pm is spitting out warnings that can cause > problems > if ran through IIS. The warnings are:- > > Use of uninitialized value $parameter in pattern match (m//) at (eval > 28) line 3. Use of uninitialized value in transliteration (tr///) at > (eval 28) line 4. Use of uninitialized value in join or string at > C:/inetpub/wwwroot/cgi- > bin/affiliate/cpanlib/CGI/Application/Plugin/DevPopup/HTTPHeaders.pm > line 73.
The first two warnings seem to come from CGI.pm, and the last one is caused by them. Show quoted text
> It would be ideal if these warnings could be surpressed.
I've added "no warnings 'uninitialized';" to the plugin, and that suppresses the warnings. Thanks for the report, Rhesa