Re^4: Porting from cgi::session to using built in activeperl management

Remove the lib.pm file you put there, it doesn't do what you think.

Keep the "use lib" line. It tells perl where it can find modules. So after that line in the script, perl looks under C:/lib/, and if it looks for CGI::Session, it will look for the file C:/lib/CGI/Session.pm

CGI::Session uses a few more internal classes besides the CGI/Session.pm file. I suggest you download the entire module from CPAN. When you unzip the file you'll find the Session directory somewhere. That directory and it's contents (including subdirs) is what you should upload to the "/lib/CGI" directory in your example.

Hope That Helps,

Comment on Re^4: Porting from cgi::session to using built in activeperl management

Replies are listed 'Best First'.
Re^5: Porting from cgi::session to using built in activeperl management by shaolindoman (Acolyte) on Jul 13, 2004 at 02:59 UTC
That still didn't work. I'm still getting an error stating: `specified CGI application misbehaved by not returning a complete set of HTTP headers` which could be anything really because the script runs fine without the `use CGI::Session` in there. At least it did work with `use lib`. I'm not sure what else to do at this point. This site is supposed to go live on the 18th of this month. Anyone have any suggestions for a windows host with MS Access that will let me use third party libraries? At least the host I'm with does have a 30-day money back policy.	[reply] [d/l] [select]
Re^6: Porting from cgi::session to using built in activeperl management by jplindstrom (Monsignor) on Jul 13, 2004 at 14:30 UTC
This is just off the top of my head. It should get you going in the right direction: You need to see the error message. It's probably in the web server's error log. Ask the web host for instructions, or read their help pages. If you can't view it, you need to force it onto the web page (instead of the generic error you get). Put a `use CGI::Carp qw(fatalsToBrowser);` [download] near the top of the script (before the CGI::Session stuff). If you still get the generic error, there might be a syntax error in your script somewhere else. Run it on a command line. /J	[reply] [d/l]