jbrugger has asked for the wisdom of the Perl Monks concerning the following question:

Ok, now i actually might have found a bug :)

Some time ago, we changed our total system to use utf-8 encoding, but now we encounter the following problems:

The first time a call is made to the server, a string is displayed correctly, but the second time, you get the weird utf-8 chars on the screen, that only show properly if you put your browser decoding back to latin1. It seems it has to do with an issue with APR::Table, that might be used by modperl to store it's data: see this link for possible details.

To overcome the problem, we now set apache to use:
PerlResponseHandler ModPerl::PerlRun
in stead of the preferred
PerlResponseHandler ModPerl::Registry
The bug does not occur now, but the advantage of using modperl is mostly lost.

Does anyone have seen the same issue and have a acceptable solution?


"We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise." - Larry Wall.