Re: porting from mod_perl1 to mod_perl2

2003-09-06 Thread Philip M. Gollucci
If you check out the changes to CGI.pm on Licoln Stiens web site, utf8 was added via a path by someone else 2.99 - 3.00 likely this is the cause. Stas Bekman wrote: Perrin Harkins wrote: I am fairly sure it is not perl5.8. I'm fairly sure it is. What is your locale set to? Are you on Red

Re: apache2, mod_perl: problem with CGI

2003-09-06 Thread Stas Bekman
speeves wrote: Stas Bekman wrote: Thanks that did it. Great. It would be nice though if the minimum rev level of the CGI.pm could be mentioned in the doc. Or maybe it is there somewhere and I skimmed over it. It's a a CGI.pm problem, really. We can't go and support all possible modules that

Re: porting from mod_perl1 to mod_perl2

2003-09-06 Thread Stas Bekman
Philip M. Gollucci wrote: If you check out the changes to CGI.pm on Licoln Stiens web site, utf8 was added via a path by someone else 2.99 - 3.00 likely this is the cause. Bart, can you try then with an earlier version? e.g. 2.93 was good for me. You can get it from here:

Re: apache2, mod_perl: problem with CGI

2003-09-06 Thread Stas Bekman
Philip M. Gollucci wrote: I'll disagree on this being a windows only problem in CGI. I'll also disagree about the version number. As late as CGI 3.00 this problem exists in Apache 1.3.27 and mod_perl 1.27 on SunOS. I believe it's not the problem Bart was talking about. You are most likely

Re: apache2, mod_perl: problem with CGI

2003-09-06 Thread Shannon Eric Peevey
Stas Bekman wrote: speeves wrote: Stas Bekman wrote: Thanks that did it. Great. It would be nice though if the minimum rev level of the CGI.pm could be mentioned in the doc. Or maybe it is there somewhere and I skimmed over it. It's a a CGI.pm problem, really. We can't go and support

Re: apache2, mod_perl: problem with CGI

2003-09-06 Thread Stas Bekman
So these are the versions required to run properly with mod_perl 2.0? Here is an updated table: Module Name Required Dist Package - Apache::AuthExpire Apache-AuthExpire-0.38 Apache::AuthNetLDAP

RE: porting from mod_perl1 to mod_perl2

2003-09-06 Thread Bart Terryn
Stas wrote: Bart, can you test whether you have the same problem when a run the same code under mod_cgi in Apache2 (with perl5.8 ofcourse)? If not, that will point the blaming finger towards mod_perl 2.0. Well I did that and guess what? mod_cgi fails as well. So it is not a mod_perl problem But

RE: porting from mod_perl1 to mod_perl2

2003-09-06 Thread Bart Terryn
I had version CGI 3.00 installed. Downgraded it to CGI 2.93, put I still have the same result. The problem as I see it that I have a form with character #8212; in it. But it is returned as character #151 from the Widows-1252 characterset. Does everybody agree that it should be returned as #8212;

Re: $r-headers_out Location and Set-Cookie

2003-09-06 Thread Michael
On Fri, Sep 05, 2003 at 10:13:36, Geoffrey Young said... actually, the return value is entirely ignored in Registry scripts - that's why we need the $r-status hack, which is not needed (or desired) in handlers. if you returned SERVER_ERROR it would still work, so long as you set $r-status

Content encoding when filtering proxyed pages

2003-09-06 Thread Esteban Fernandez Stafford
Hello all, I have a machine acting as a proxy using mod_perl-1.99_09 with apache 2.0.46. This proxy is supposed to filter all html content. So far I have achieved most of my project's goals. But there is one issue I can't get straight, this is when the proxy gets a page that is encoded (like in

Re: CPAN module Apache::Emulator

2003-09-06 Thread Adam Kennedy
For those interested, I've been doing a general clean up of the code ( shrinking the code size down mainly ), prior to starting further work on it. Code available on request. My intentions is to keep it as light as possible. While Apache::Fake seems to be able to do a very large amount of