there seems to be problems encoding german "umlaute" in the
request path info. This e.g. is the case in the admin
user browser when editing a user with "�" in the username.
The username is part of the generated path as /entityid/"username"
e.g. /entityid/m%E4rtin where "�" is encoded as %E4 (correct).
When extracting the username on the server decoding won't work !
This already seems to be a problem of tomcat (4.1.18 and .24),
because the username already is wrong in the HttpServletRequest ...
Everything works fine, if you add the user as query parameter
in the url instead of as part of the path (jslink.addQueryData()
instead of addPathInfo()), then the user is decoded correctly !
We use jetspeed-1.4-b4 with tomcat 4.1.24.
The html encoding in media.xreg is
<character-set>8859_1</character-set>
This works perfect when using parameters and fails when using
path info !!!?
Is there a way to keep the username in the path without
decoding problems, so we don't have to change all the templates ?
thanks a lot in advance,
Martin
................................
martin maidhof
[EMAIL PROTECTED] | fon: +49-(0)69-759003-14
w e m o v e d i g i t a l s o l u t i o n s ... http://www.wemove.com
----- Original Message -----
From: "Aurelien Pernoud" <[EMAIL PROTECTED]>
To: "'Jetspeed Users List'" <[EMAIL PROTECTED]>
Sent: Wednesday, June 04, 2003 2:44 PM
Subject: RE: encoding problem
>
> There has been a change between b3 and b4 relative to encoding :
>
> Here's how jetspeed looks for the encoding to use now, if you use the right
> way to grab parameters (see next) :
> 1) the character encoding used in the body of the request.
> 2) character-set parameter in media.xreg
> 3) content.defaultencoding in JetspeedResources.properties
> 4) US-ASCII
>
> so check all those parameters to see if one may be wrong for you.
> Although there is two ways to "grab" your request parameters in your
> portlets :
>
> data.getRequest().getParameter(aParameterName) : WRONG
> data.getParameters().getString(aParameterName) : RIGHT
>
> Cause Servlet 2.2 API is known to be buggy when encoding is different from
> ISO8859-1, so you should better use the parameterparser provided in jetspeed
> (second method).
>
> So check all this parameters and see where your trouble comes from.
>
> HTH,
> Aurelien
>
> PS : if you're using tomcat 3, then you're meeting a specific bug from it,
> and right now jetspeed is still buggy with tomcat 3.
>
> Ivan a ecrit :
>
> > Hello everybody,
> >
> > I got a problem and I'm not sure if it's a bug or a
> > misconfiguration of my system.
> >
> > I had a 1.4b3 portal working ok, and after the upgrade
> > to 1.4b4 some portlets are not sending the form post info well.
> >
> > this is where It sent "Ivan" now it sends "IvC!n", it
> > looks like some ascii to hex change...
> >
> > Anyone knows what can it happen???
> >
> > Many thanks in advance.
> > Ivan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
