in the java side of ajp13, it is pretty much assumed that strings are
iso-8859-1 encoded. (i'm not sure how things that deal with
MessageBytes that come out of ajp13 deal with encoding...).
is this a potential problem? i realize that for things like standard
header names this will generally not be a problem. but would it be
worthwhile to send an encoding across from the webserver to the
container in ajp14? or, can iso-8859-1 be assumed, and if a
content-type header is present and specifies an encoding, it can be
pulled out of there?
i'm sensitive to these issues now, as i'm currently going through the
'joy' of an i18n/l10n release ;)
-kevin.
GOMEZ Henri wrote:
>
> Hi to all,
>
> You could find attached a proposal of evolution to
> the current Apache JServ Protocol version 1.3,
> also known as ajp13.
>
> Let start the comments, questions, remarks cycle.....
>
> PS : I've not cover here the full protocol but only the add-on
> from ajp13.
>
> -
> Henri Gomez ___[_]____
> EMAIL : [EMAIL PROTECTED] (. .)
> PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
> PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>
> ------------------------------------------------------------------------
> Name: AJPv14.txt
> AJPv14.txt Type: Plain Text (text/plain)
> Encoding: quoted-printable
