RE: Getting a request in a non English character

2004-04-25 Thread Mark Thomas
useBodyEncodingForURI=true It still don't work Yair -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: 20 2004 23:29 To: 'Tomcat Users List' Subject: RE: Getting a request in a non English character http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config

RE: Getting a request in a non English character

2004-04-25 Thread yair . fine
); And this some how doesn't work , Any suggestions? Regard Yair -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Sunday, April 25, 2004 5:09 PM To: 'Tomcat Users List' Subject: RE: Getting a request in a non English character

RE: Getting a request in a non English character

2004-04-25 Thread Mark Thomas
Try specifying the encoding in your client as as windows-1255 Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, April 25, 2004 6:28 PM To: [EMAIL PROTECTED] Subject: RE: Getting a request in a non English character Mark, Your client

Re: Getting a request in a non English character

2004-04-25 Thread Paul Gregoire
: Sunday, April 25, 2004 6:28 PM To: [EMAIL PROTECTED] Subject: RE: Getting a request in a non English character Mark, Your client and servlet works!! Thanks. Now I have only one request, I tried to modify the client, that instead of preparing a predefined line: String data = name

RE: Getting a request in a non English character

2004-04-25 Thread Yair Fine
Mark , Sorry for nagging you )-; but this is exacly what I did : //THE CLIENT: import java.io.*; import java.net.*; public class HttpClientHebrew5Test { public static void main(String[] args) { try { String host = 127.0.0.1; String port = 8083;

RE: Getting a request in a non English character

2004-04-24 Thread Yair Fine
- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: 20 2004 23:29 To: 'Tomcat Users List' Subject: RE: Getting a request in a non English character http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/http.html Tomcat 4 ships with the same connector but the docs aren't quite up to date

RE: Getting a request in a non English character

2004-04-20 Thread Yansheng Lin
Hi, I don't have that book, so I am not sure if there is a new version. But I think you can try one of the constructors in the String class. String value = req.getParameter(param); String valueInUnicode = new String(value.getBytes(Cp1255), UTF8); -Yan -Original Message- From: [EMAIL

RE: Getting a request in a non English character

2004-04-20 Thread yair . fine
' Subject: RE: Getting a request in a non English character Hi, I don't have that book, so I am not sure if there is a new version. But I think you can try one of the constructors in the String class. String value = req.getParameter(param); String valueInUnicode = new String(value.getBytes

RE: Getting a request in a non English character

2004-04-20 Thread Yansheng Lin
To: [EMAIL PROTECTED] Subject: RE: Getting a request in a non English character Thanks, But I tried and it doesn't work Is it because it is in the GET request and not in POST Maybe Tomcat don't know how to deal with Charset Cp1255 requests? -Original Message- From: Yansheng Lin [mailto

RE: Getting a request in a non English character

2004-04-20 Thread Mark Thomas
You might find the text below useful. It is my standard text on character encoding. Mark REQUESTS There are a number of situations where there may be a requirement to use non-US ASCII characters in a URI. These include: - Parameters in the query string - Servlet paths There is a

RE: Getting a request in a non English character

2004-04-20 Thread Yair Fine
-Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: 20 2004 21:19 To: 'Tomcat Users List' Subject: RE: Getting a request in a non English character You might find the text below useful. It is my standard text on character encoding. Mark REQUESTS

RE: Getting a request in a non English character

2004-04-20 Thread Mark Thomas
List' Subject: RE: Getting a request in a non English character Hi Mark, Thanks for your reply , You wrote : The Coyote HTTP/1.1 connector has a useBodyEncodingForURI attribute which if set to true will use the request body encoding to decode Where can I configure