I can't reproduce the problem with the cvs version of mod_perl, would you consider giving it a try?
I tried the CVS version, and no problems.. so it is fixed there.
Previously I found that pre-loading the CGI's with RegistryLoader also avoided the errors.
Yes, it was due to a false assumption in the slurp_filename implementation... now fixed.
Either way, now I can get back to work! :-)
Coolio. Once we find and fix a few more significant bugs we will get a new release out.
Also, you probably want to add:
PerlOptions +ParseHeaders
and always print the content-type header from your scripts. Even though httpd-2.0 lets you to get away without it (apache-1.3 doesn't) it's not a very good programming practice. (e.g. httpd-2.0 can suddenly start requiring this header to be present)
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
