RE: URL encoding for request

2003-10-23 Thread Fleischer Roman
with URL encoded searchString everything works. What is my error? Thanks -Original Message- From: Joerg Heinicke [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 23. Oktober 2003 01:19 To: [EMAIL PROTECTED] Subject: Re: URL encoding for request Hello Roman, for the request generator

Re: URL encoding for request

2003-10-23 Thread Joerg Heinicke
the searchPageResult direct in the browser with URL encoded searchString everything works. What is my error? Thanks -Original Message- From: Joerg Heinicke [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 23. Oktober 2003 01:19 To: [EMAIL PROTECTED] Subject: Re: URL encoding for request Hello Roman

RE: URL encoding for request

2003-10-23 Thread Fleischer Roman
:41 To: [EMAIL PROTECTED] Subject: Re: URL encoding for request 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

Re: URL encoding for request

2003-10-23 Thread Joerg Heinicke
: Donnerstag, 23. Oktober 2003 09:41 To: [EMAIL PROTECTED] Subject: Re: URL encoding for request 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

RE: URL encoding for request

2003-10-23 Thread Conal Tuohy
October 2003 10:55 To: [EMAIL PROTECTED] Subject: Re: URL encoding for request On 23.10.2003 13:35, Fleischer Roman wrote: I think it is a problem for the used searcheDatabase Servlet. For the result I use a file-generator, but in reality it is a service like: map:generate src=http

Re: URL encoding for request

2003-10-22 Thread Joerg Heinicke
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