Hi, the fdat empty problem is actually a mod_perl problem with environment variables on windows and the newest Embperl version contains a workaround for it. I am not sure if this problem can occur on Unix too. It may under some circumstances arise when you load mod_perl as DSO (via LoadModule in your httpd.conf). I personaly never have seen this problem on Unix, but I normaly link mod_perl staticly into Apache for all out production severs.
Gerald P.S. Please send further questions to the embperl mailing list so others can participate ----- Original Message ----- From: "Michael Stairs" <[EMAIL PROTECTED]> To: "'Gerald Richter'" <[EMAIL PROTECTED]> Sent: Thursday, January 03, 2002 10:06 PM Subject: empty fdat > Hi, > > We have a large site that has been using embperl/modperl for a number of > years. We've had a class of errors that have always occurred but as the > traffic to our site has increased the problem has become more of an issue. > Sometimes fdat is not properly populated when scripts are called causing > subsequent backend problems. By manually forcing the population of fdat, > using CGI.pm to process the parameters at the start of scripts when fdat is > empty, I'm able to eliminate a large percentage of these errors. We have a > mix of gets and posts throughout our site. I noticed that you mentioned in > the mailinglist archive that a similiar problem/fix under windows addressed > by the latest release. Does the error/problem come from a windows browser or > windows NT web server? We are using Redhat web servers and I'm was wondering > if the fix would solve our problems. I don't want to rush out and update all > our web servers with new embperl/modperl/apache unless it will fix things. > > -- > Michael Stairs > Senior Web Developer > Lavalife Inc. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
