for the request generator the decoding is okay. It gives the request params in their string representation in an XML structure. It knows nothing about an URL encoded string. (%C3%9F is URl encoded, not UTF encoded!!)
Maybe it's better to tell us your use case. If you transform the output of the request generator back into a HTML page with links, the @href will be URL encoded again - at least that should be done by the XML serializer.
Joerg
On 21.10.2003 14:10, Fleischer Roman wrote:
Hello,
i have some problems with URL encoding. I call a matcher in this form:
http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9Fharz&searchMLFB=&searc
h=result...
(%C3%9F is the german "ss")
In the matcher i call a request generator and a xml-serializer.
The result is:
...
<h:requestParameters>
<h:parameter name="searchString">
<h:value>Gießharz</h:value> </h:parameter>
<h:parameter name="search">
<h:value>result</h:value>
...
Why is the parameter searchString transformed? How can i aviod the transforming? I need this param UTF-8 encoded (like in the calling URL)
Any idea? Thanks...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
