> > > When CGI fails, does it contain any usefull information ? > > It's empty. Always. >
ok, I just wanted to make sure it didn't get lost, because there was nothing in the Embperl error message. So we have verified that CGI.pm really doesn't set's $@ > > Also the user often (but not always) gets a '500 server error' message. > This happens at least 20 times a day on our site, so I don't think it > is the user pressing stop. > They will see the 500 error when you see message in the error log I guess. > > Other things that may be useful: > > - This happens in a script that is called as a CGI, not through mod perl. > I have not seen it happen through mod perl. Unfortunately a bug in mod proxy > means that I have to run it as a CGI. > > - It is an upload script that handles large files - usually over 1MB > > - I also use CGI::Cookie in this script. > I have currently no idea what is happeing. The only way I see to track this down, is to put logging message inside of CGI.pm itself. I good place to start is the function read_multipart. Put some warns inside to see where it might fail. Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
