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
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
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:
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
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
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
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
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;
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
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
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
11 matches
Mail list logo