Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 18388 invoked from network); 23 Oct 2003 07:40:54 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 23 Oct 2003 07:40:54 -0000 Received: (qmail 12969 invoked by uid 500); 23 Oct 2003 07:40:22 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 12954 invoked by uid 500); 23 Oct 2003 07:40:22 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 12941 invoked from network); 23 Oct 2003 07:40:21 -0000 Received: from unknown (HELO sati.virbus.de) (145.253.246.81) by daedalus.apache.org with SMTP; 23 Oct 2003 07:40:21 -0000 Received: from sati.virbus.de (localhost [127.0.0.1]) by localhost (SMTP Server) with ESMTP id CB63D166A6A for ; Thu, 23 Oct 2003 09:40:33 +0200 (MEST) Received: from virbus.de (a183069.studnetz.uni-leipzig.de [139.18.183.69]) by sati.virbus.de (SMTP Server) with ESMTP id 856E2166A62 for ; Thu, 23 Oct 2003 09:40:33 +0200 (MEST) Message-ID: <3F97860D.2050008@virbus.de> Date: Thu, 23 Oct 2003 09:41:01 +0200 From: Joerg Heinicke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: de-de, de, en-gb, en-us, en MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: URL encoding for request References: <7F118E709193D711805F0002A540AC2E16A451@erlm512a.erl9.siemens.de> In-Reply-To: <7F118E709193D711805F0002A540AC2E16A451@erlm512a.erl9.siemens.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Seems to be more weird than it should be. In your database there is "Gie�harz" I think and not the URL encoded form of it. Furthermore the string is correctly in your pipelines, so everything should work. But some representations of this string are not correct, so that they don't match. One of them is the search result HTML ("Your search for "GieEUR?harz" has no hits."). I guess you have to debug around a bit where the string is "Gie�harz" and where not. It should always be in this representation internally. What about encoding (ISO-8859-1 vs. UTF-8)? How does your searchPageResult pipeline look like? Joerg On 23.10.2003 09:11, Fleischer Roman wrote: > Hello Joerg, > > thank you for the quick answer. I will tell my case, resp. show my problem. > I use a search form with the input field searchString. The form action is > OCIprod (a matcher in the cocoon sitemap). > When i look to the log-files the request is URL encoded > (http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9Fharz&searchMLFB=&sear > c....) > > The OCI prod matcher looks like this: > > > > > > > > > In the stylesheet product.xsl i use a cinclude to show the search result > select="request:requestParameters/request:parameter[@name='searchString']/re > quest:value/text()"/> > ... > > src="cocoon:/searchPageResult?lang={$lang}&searchString={$searchString}" > /> > > > Now the param $searchString has the value "Gie�harz" instead of > "Gie%C3%9Fharz" and can not be found in the database. I get an error on the > searchPage result page like "Your search for "GieEUR?harz" has no hits. If I > call the searchPageResult direct in the browser with URL encoded > searchString everything works. > > What is my error? > Thanks > > > -----Original Message----- > From: Joerg Heinicke [mailto:jheinicke@virbus.de] > Sent: Donnerstag, 23. Oktober 2003 01:19 > To: users@cocoon.apache.org > Subject: Re: URL encoding for request > > > Hello Roman, > > 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: >>... >> >> >> Gie�harz >> >> >> result >>... >> >>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: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org