Re: perl problem in 2.7

[Marc Espie <Marc_(_dot_)_Espie_(_at_)_liafa_(_dot_)_jussieu_(_dot_)_fr>]

On Wed, Apr 19, 2000 at 01:30:38AM -0700, Jack Culpepper wrote:
> I have a little web interface that uses CGI.pm and CGI/Cookie.pm, and runs
> just fine on 2.6.  When I moved everything over to 2.7, the cookie stuff
> stopped working.  I have traced the problem to the fetch function in
> Cookie.pm -- $ENV{HTTP_COOKIE} evaluates to nothing in 2.7, and something in 
> 2.6.  I have looked at the traffic on the network to make sure my cookie is
> getting sent to the web server.  It is.  So the problem lies in the way the
> web server is invoking my perl script, I think.

Which version of CGI.pm ?
CGI.pm is a *big* ugly thing, which does some rather dirty tricks. I'm not
surprised something went wrong... but we can't help you without a version
number.

> This may or may not be attributable to me not doing something correctly,
> so has anyone had *success* with fetching cookies in 2.7?
> 
> Another slightly annoying thing with the new version of perl is that when I
> call my scripts from the command line, I am not prompted for name=value pairs
> when I create a new CGI object.  However, this is mostly just helpful for
> debugging stuff.  The CGI object still works as expected from the web browser
> perspective.  Again, I have not been keeping up with all the stuff that went
> in to perl 5.6, so I may just be calling things wrong now...  It is annoying
> that the behavior of stuff has changed tho...  Shouldn't the old way of doing
> stuff still work?
To the best of my knowledge, CGI.pm has always worked that way, specifically
for debugging issues. There is probably a tweak somewhere that you can put
in a BEGIN {} block to get it NOT to process your script in interactive mode.
-- 
	Marc Espie		
|anime, sf, juggling, unicycle, acrobatics, comics...
|AmigaOS, OpenBSD, C++, perl, Icon, PostScript...
| `real programmers don't die, they just get out of beta'