Hi,
POST data is read directly from the socket and can only be read once.
You must save the POST'd data in a data structure that is passed or
available to the different handlers in order to access it multiple
times.
Here is a good explanation of the process, they use a different method
than the o
';
> > in the global mod_perl startup script.
> >
>
> well, that works.
> Rob, that should probably help you.
> The difference with PERL_UNICODE "SAD" seems to be that it will not
> automatically consider @ARGV as utf-8.
>
>
>
>
>
> &
ECTED]> wrote:
> Maybe you need to use PerlSetEnv ?
>
>
>
> - Original Message -
> From: "Rob French" <[EMAIL PROTECTED]>
> To: "André Warnier" <[EMAIL PROTECTED]>
> Cc:
> Sent: Wednesday, March 19, 2008 2:41 PM
> Subjec
; I have tried the same thing in the meantime under Apache 2.x/mod_perl
> 2.x, and I seem to have the same problem.
>
> I have one more question : where exactly do you set PERL_UNICODE ?
>
>
>
>
>
> Rob French wrote:
> > Hi André,
> >
> > Yes, I tr
: even with the decoding layer set, that does not necessarily mean
> that all data you read will end up with the utf8 flag set. It depends
> on the data. But in your case, if you are really using the same file
> data in both tests you show below, then it seems a valid test.
>
> An
I have recently started converting one of our webapps to make it fully
UTF-8 compliant. All input/output from the webapp will be encoded as
UTF-8. As such, I am trying to use the PERL_UNICODE env variable to
enable UTF-8 flagging on all input/output streams. This works with
standalone Perl scripts
