Hi people,
I use Tomcat 5.5.9 with Apache 2.0.54 and jk 1.2.10 to serve my websites. I
want to set custom error pages to be served when an error like 404, 500 etc.
occurs. The website uses the iso-8859-9 character set on every page, and the
error pages are encoded with iso-8859-9 too.
Only
Hello!
I've tried my luck with Tomcat 5.5 and found that it behaves different
than 5.0.27 does as regards character encoding. Somehow the conversion
from ISO-8859-1 to UTF-8 doesn't work as it should. This may well be
due to a misconfiguration. See below for the JSP document and the two
:)
-Original Message-
From: Anton Tagunov [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 06, 2003 5:46 AM
To: Tomcat Users List
Subject: Re: Character Encoding problem (umlauts, etc).
Hello Robert!
Robert Priest [EMAIL PROTECTED] wrote:
RP I am requesting file :
RP
Robert Priest schrieb:
I have a servlet that catches a request for a file.
How is the request sent?
If sent via an HTML form, you need to include the accept-charset=UTF-8
attribute into your form tag
Thomas
-
To
]
Sent: 08 September 2003 14:18
To: 'Tomcat Users List'
Subject: RE: Character Encoding problem (umlauts, etc).
Thanks for the information Anton. But just getting rid of umlauts or other
international characters is not an option when you have clients that use
your software in other countries
Hello Robert!
RP Thanks for the information Anton. But just getting rid of umlauts or other
RP international characters is not an option when you have clients that use
RP your software in other countries, that have those special characters. We
RP cannot rename user files or changed that data.
Hello Robert!
Robert Priest [EMAIL PROTECTED] wrote:
RP I am requesting file :
RP /38CF278C0186B466222FC48571080B83/51/dms00051/äää.txt
RP but what is coming across in the request is:
RP /38CF278C0186B466222FC48571080B83/51/dms00051/???.txt
Probably your browser is sending it that way?
I guess
I have a servlet that catches a request for a file.
But if that file has characters such as an umlaut in it (for example: ä),
the path info is all wrong.
For example: I am requesting file :
/38CF278C0186B466222FC48571080B83/51/dms00051/äää.txt
but what is coming across in the
This is in a JSP page (which of course becomes a servlet).
Do I have to set the encoding in Tomcat perhaps?
-Original Message-
From: Robert Priest [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 04, 2003 5:16 PM
To: '[EMAIL PROTECTED]'
Subject: Character Encoding problem (umlauts
have to set the encoding in Tomcat perhaps?
-Original Message-
From: Robert Priest [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 04, 2003 5:16 PM
To: '[EMAIL PROTECTED]'
Subject: Character Encoding problem (umlauts, etc).
I have a servlet that catches a request for a file
On Wednesday 28 August 2002 13:17, you wrote:
Hi
I am using tomact 4.0.4 and JDK1.3.1
I am trying to read parameter in hebrew from the URL but get '???' writing
Hebrew to the browser works fine
I can not use req.setCharacterEncoding(java.lang.String env) (can not
compile the code when I
Nehemia Litterat [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Hi
I am using tomact 4.0.4 and JDK1.3.1
I am trying to read parameter in hebrew from the URL but get '???' writing
Hebrew to the browser works fine
I can not use
Hi
I am using tomact 4.0.4 and JDK1.3.1
I am trying to read parameter in hebrew from the URL but get '???' writing Hebrew to
the browser works fine
I can not use req.setCharacterEncoding(java.lang.String env) (can not compile the code
when I am using it)
is there a way to go around it. I
Perhaps something like this is tomcat/bin/setclasspath.sh
JAVA_OPTS=-Dfile.encoding=ISO-8859-1
(with you ISO configuration, of course).
Fabio.
Nehemia Litterat wrote:
Hi
I am using tomact 4.0.4 and JDK1.3.1
I am trying to read parameter in hebrew from the URL but get '???' writing Hebrew
hi,
since two weeks I'm fighting with a character encoding problem without
success: I send a JSP form to a Tomcat 4.03 servlet and log the form input
with log4j into a file and into a database. Running on a german server with
Suse Linux everything works fine. Now I installed Tomcat and servlet
All,
Tomcat 4.0.1
Apache 1.3
WARP
Solaris 8
JDK 1.2/1.3
Does anyone know why a servlet would suddenly start displaying non-breaking
spaces (#160;) as question marks (?) when the JDK/SDK is upgraded from 1.2
to 1.3? Very odd behaviour! Like a rash - question marks all over the place
:)
The
and this
works very well for solving encoding problem with JSP:
///
//
// How to solve the character encoding problem with JSP
Hi,
I know that this is a popular (!?) problem in tomcat. Dur despite my efforts I could
not find any solution. Here it goes:
We have jsp page in encoding type ISO-8859-9. With the line
%@ page contentType = "text/html; charset=ISO-8859-9" %
we define the encoding type of the document.
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 02, 2001 10:33 AM
To: [EMAIL PROTECTED]
Subject: Character Encoding Problem
Hi,
I know that this is a popular (!?) problem in tomcat. Dur
despite my efforts I could not find any solution. Here it goes:
We have
Kimden: Tnu Pld [EMAIL PROTECTED]
Tarih: 2001/07/02 Mon AM 10:48:10 GMT+03:00
Kime: "'[EMAIL PROTECTED]'" [EMAIL PROTECTED]
Konu: RE: Character Encoding Problem
Hi,
You should compile the java classes with ISO-8859-9 encoding.
Look at the -encoding flag of the 'javac
e does not print the
strErroMsg variable correctly.
How can this problem be solved?
Thanks,
Oner Necip Hamali.
Kimden: [EMAIL PROTECTED]
Tarih: 2001/07/02 Mon PM 12:16:03 GMT+03:00
Kime: [EMAIL PROTECTED]
Konu: lgi:RE: Character Encoding Problem
Kimden: Tnu Pld [EMAIL PROTECTED]
Tarih: 200
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 02, 2001 11:16 AM
To: [EMAIL PROTECTED]
Subject: ?lgi:RE: Character Encoding Problem
Kimden: Tõnu Põld [EMAIL PROTECTED]
Tarih: 2001/07/02 Mon AM 10:48:10 GMT+03:00
Kime: '[EMAIL PROTECTED]'
[EMAIL
Kimden: Tnu Pld [EMAIL PROTECTED]
Tarih: 2001/07/02 Mon AM 11:55:51 GMT+03:00
Kime: "'[EMAIL PROTECTED]'" [EMAIL PROTECTED]
Konu: RE: ?lgi:RE: Character Encoding Problem
Just a thought about the jsp:include... problem:
try to place the "%@page contentType=" in e
When reading bytes from file with FileReader the default character encoding
is used.
I think you must specify your own encoding when reading the file.
I'll try that. But the same compiled classes and the same jdk version works well
with Resin JSP Server and the files. The problem
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 02, 2001 3:34 PM
To: [EMAIL PROTECTED]
Subject: RE: Character Encoding Problem
When reading bytes from file with FileReader the default
character encoding
is used.
I think you must specify your own encoding when
25 matches
Mail list logo
