-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
German Starz,
On 12/18/11 7:26 AM, starz10de wrote:
> I a login page (it has utf-8) I checked this also manually; after
> login is successful a jsp page will be called to enter the query.
> This jsp page use iso encoding although inside it utf-8 is
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 12/17/11 9:37 AM, André Warnier wrote:
> I do not see anything in the above that submits anything with an
> "umlaut".
The form could have additional that were not included in the OP.
> This is a "GET" request, so anything submitted would
-
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.nabble.com/URIEncoding-tp32989250p33005252.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
starz10de wrote:
One of my try to solve the problem is to use utf-8 in my html page as well as
in my backend. It doesn’t work because the reason was that the Browser
change automatically to iso encoding. Today I checked the browser encoding
before submit the query and saw that it use iso although
he
server as UTF-8.
If the server receives the request in one encoding, but is expecting another, then it will
not understand the request properly, and (in your application) probably not find anything.
In other words :
- if you tell the server : URIencoding="UTF-8"
but the requests come i
n the server we have tomcat running and provide services for many
> instances. After I played my application in the server, I had problem with
> query which have special language character. After long time, I could find
> where is the problem. The problem was in server.xml where the URIEnco
">
>>
>>
>>
>>
>>
>>>Try the following, directly in your browser's URL bar :
>>>http://localhost:8080/Search/main?name=böse zeichen
>>>(note the ö-umlaut)
>>>What
s that do ?
>
> it doesn't work because when I submit the query I see just the main menu
> jsp in the link bar.
>
> Thanks for your response, is there any problem in what I mentioned?
>
>
--
View this message in context:
http://old.nabble.com/URIEncoding-tp
nning and provide services for many
instances.
After I played my application in the server, I had problem with query
which
have special language character. After long time, I could find where is
the
problem. The problem was in server.xml where the URIEncoding is set to
"UTF-8". I made test and
nguage character. After long time, I could find where is
>> the
>> problem. The problem was in server.xml where the URIEncoding is set to
>> "UTF-8". I made test and just removed this line or set it to "ISO-8859-1"
>> and all was perfect. My question here
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 12/16/11 3:37 PM, André Warnier wrote:
> 4) Thus, if your pages are UTF-8, then any link in the page which
> "calls" the server, is going to send all values to the server in
> the UTF-8 character set.
I'm not so sure about that. Firefox ha
problem with query which
have special language character. After long time, I could find where is the
problem. The problem was in server.xml where the URIEncoding is set to
"UTF-8". I made test and just removed this line or set it to "ISO-8859-1"
and all was perfect. My question he
which
have special language character. After long time, I could find where is the
problem. The problem was in server.xml where the URIEncoding is set to
"UTF-8". I made test and just removed this line or set it to "ISO-8859-1"
and all was perfect. My question here is it
imrezol wrote:
Hi!
I set URIEncoding="UTF-8" at http connector in server.xml:
restart tomcat service and after that type an url with special charaters
like this:
http://localhost:8080/mywebapp/docs/Felhasználói_kézikönyv.pdf<http://localhost:8080/mywebapp/docs/Felhaszn%C3%A1
Sorry, it was my mistake.
On 64 bit version webapp name was MyWebApp
On 32 bit version webapp name was mywebapp
On Fri, Dec 10, 2010 at 13:54, imrezol wrote:
> Hi!
>
> I set URIEncoding="UTF-8" at http connector in server.xml:
>
>
Hi!
I set URIEncoding="UTF-8" at http connector in server.xml:
restart tomcat service and after that type an url with special charaters
like this:
http://localhost:8080/mywebapp/docs/Felhasználói_kézikönyv.pdf<http://localhost:8080/mywebapp/docs/Felhaszn%C3%A1l%C3%B3i_k%C3%A9zik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
André Warnier wrote:
>
> The OP is talking about UTF-16, not UTF-8.
I understand. I was trying to contrast UTF-8 and UTF-16, apparently
unsuccessfully.
> What you are saying above about ASCII/UTF-8 is true, if one restricts
> oneself to stri
Replying to myself :
André Warnier wrote:
My own name, expressed in the
Unicode alphabet and encoded in UTF-8, occupies 6 bytes, not 7.
I meant "6 bytes, not 5", of course.
It rather weakens my argument when I mix-up my own byte counts...
--
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
André Warnier wrote:
Could you tell us *why* exactly you [are trying to use UTF-16]?
It is rather unusual, as it supposes that you expect all clients to
encode their requested URI's in UTF-16 prior to sending the r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
André Warnier wrote:
> Could you tell us *why* exactly you [are trying to use UTF-16]?
> It is rather unusual, as it supposes that you expect all clients to
> encode their requested URI's in UTF-16 prior to sending the request to
> Tomcat on th
Nayyer Kamran wrote:
Hello,
I am facing problem in accessing deployed modules once I configured connector's
URIEncoding to "UTF-16" in server.xml.
Hi.
Could you tell us *why* exactly you did set this attribute ?
It is rather unusual, as it supposes that you expect all cli
Hello,
I am facing problem in accessing deployed modules once I configured connector's
URIEncoding to "UTF-16" in server.xml. The log is showing nothing unusual but
no web module is accessible and throwing http status 404.
Can you some one told me what is the reaso
to
set the URIEncoding attribute on the Tomcat connector as well. To
avoid restarting Tomcat for each application configuration under
test, I'm using JMX in Ant to change the value of the URIEncoding
attribute for the tests for each configuration. The sequence is
basically
1. Install web applic
AFAIK, we had to add two things to support UTF-8 in our environment:
1. We had to add a Filter to Tomcat to set the encoding on every
request to UTF-8, see this page: http://wiki.apache.org/tomcat/Tomcat/UTF-8
2. Add "JkOptions +ForwardURICompatUnparsed" to our apache config file
in sites-
hi,
My application was running on Tomcat server 5.5.17 version. it was working
fine with UTF-8 on this version.
Now Iam using Tomcat 5.5.23 server. this version is not able to process
my UTF-8 requests.
I made the below changes in my server.xml, still it is not working.
thanks in adv.
Rohit Seth wrote:
> 1. Added URIEncoding="UTF-8" in connector element.
> 2. Modified code to set encoding for request and response.
>
> After these changes we are observing following behavior:
>
> 1. If url doesn't contain any special character, everything is f
I tried to search the issue in forum but couldn't find any solution. We need
to support special characters in URL (like ます or õñü). After going through
various articles we have done following changes to accomplish the same
1. Added URIEncoding="UTF-8" in connector element.
2. M
Thanks for your help, that answers my question pretty well :)
Caldarale, Charles R a écrit :
From: Frederic Bastian [mailto:[EMAIL PROTECTED]
Subject: Re: URIEncoding
Could you tell me a bit more about how MBean can solve my problem ? I
never used it.
Tomcat creates MBeans for most of
> From: Frederic Bastian [mailto:[EMAIL PROTECTED]
> Subject: Re: URIEncoding
>
> Could you tell me a bit more about how MBean can solve my problem ? I
> never used it.
Tomcat creates MBeans for most of its internal objects, including
connectors:
http://tomcat.apache.org/tomcat
Caldarale, Charles R a écrit :
Once again, it's available via the MBean that Tomcat creates for each
element.
I'm sorry i should have missed your reply.
Could you tell me a bit more about how MBean can solve my problem ? I
never used it.
-
> From: Frederic Bastian [mailto:[EMAIL PROTECTED]
> Subject: Re: URIEncoding
>
> how to know the Connector URIEncoding value, inside
> your application ? :)
Once again, it's available via the MBean that Tomcat creates for each
element.
- Chuck
THIS COMMUNICATION MAY
your own tomcat server, you need to
URLEncode the parameters in the same character encoding than the
URIEncoding.
What makes you think that the Connector has the right answer in the
first place?
Because it is the Connector that will read your URI ;) And so, when
URLEncoding links
elevant, here.
> For instance, you
> can set the response character encoding to UTF-8 in order to display
> your html in UTF-8, and set the Connector URIEncoding to ISO-8859-1 to
> read URI in ISO-8859-1 (and so, you have to encode your URI in ISO-8859-1).
Yes, except that most brows
:) request.getCharacterEncoding() is different
from URIEncoding. The request character encoding
determines in which character encoding the parameters value will be
return to you.
My mistake. I meant response.getCharacterEncoding().
But it doesn't determine in wich character encoding the URI has to be
CharacterEncoding() is different
> from URIEncoding. The request character encoding
> determines in which character encoding the parameters value will be
> return to you.
My mistake. I meant response.getCharacterEncoding().
> But it doesn't determine in wich character encoding
Christopher Schultz a écrit :
You want to do this:
java.net.URLEncoder.encode(myParam, request.getCharacterEncoding());
This does not work :) request.getCharacterEncoding() is different from
URIEncoding. The request character encoding determines in
wich character encodig the parameters
atever
Tomcat (or the browser) is using for URIEncoding.
You want to do this:
java.net.URLEncoder.encode(myParam, request.getCharacterEncoding());
Or, you could do what everybody else in the world does and use a tag
library or some other tool to emit URLs including parameters, etc.
- -chris
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
>> From: Frederic Bastian [mailto:[EMAIL PROTECTED]
>> Subject: Re: URIEncoding
>>
>> Is there a way to get the value of the param URIEncoding of the
>> Connector, so your cod
;
> By default, Tomcat will read this url in ISO-8859-1.
Yes, but you said that you changed the to use UTF-8. Is it
not working? Or, are you looking for an alternative so that you don't
/have to/ set the 's URIEncoding?
> If I add into server.xml the attribut URIEncoding=
> From: Frederic Bastian [mailto:[EMAIL PROTECTED]
> Subject: Re: URIEncoding
>
> The point is that I need to use the
> java.net.URLEncoder.encode() method,
> e.g. java.net.URLEncoder.encode(myParam, "UTF-8").
O.k., so now it appears you need to know the encoding i
Caldarale, Charles R a écrit :
From: Frederic Bastian [mailto:[EMAIL PROTECTED]
Subject: Re: URIEncoding
Is there a way to get the value of the param URIEncoding of the
Connector, so your code will work, whatever the char encoding of the
Connector is ?
I'm confused. If the al
> From: Frederic Bastian [mailto:[EMAIL PROTECTED]
> Subject: Re: URIEncoding
>
> Is there a way to get the value of the param URIEncoding of the
> Connector, so your code will work, whatever the char encoding of the
> Connector is ?
I'm confused. If the already has
Thx a lot Pulkit, it works just fine.
But my aim is to make portability easier ; What happens if the
URIEncoding of the Connector is not "UTF-8" or "ISO-8859-1", but a
different char encoding ?
Your pseudo-code won't work anymore :(
Is there a way to get the value of
uest.getParameter("query") will return an incorrect value.
The solution you proposed won't help Tomcat to return a correct value
with the "getParameter" method.
If I add into server.xml the attribut URIEncoding="UTF-8" to the
Connector, Tomcat will correctly read
1. So
HttpServletRequest.getParameter("query") will return an incorrect value.
The solution you proposed won't help Tomcat to return a correct value
with the "getParameter" method.
If I add into server.xml the attribut URIEncoding="UTF-8" to the
Connector, Tomcat will correctly
Hi Frederic,
I don't know about HttpSession. for settign the URIEncoding.
But you could always do somethign along the lines of:
String uri_utf8 = new String (uri.getBytes("iso-8859-1"), "UTF-8");
inside the application.
On 7/26/07, Frederic Bastian <[EMAIL PROTECTE
Hi folks :)
I need my URI to be in UTF-8. In server.xml, I added to the Connector
the attribut : URIEncoding="UTF-8"
This works well. But my question is :
Is there a way to define the URIEncoding in the application itself ?
For instance, you can modify the session timeout in the a
Mike Wannamaker wrote:
> I can specify URIEncoding="UTF-8" in Tomcat's connector settings within the
> server.xml file. Now, my Tomcat server correctly reads the URL GET
> parameters correctly...sending out "Hello, José!" or "Hello, 田中!" as
> e
+ encoding);
request.setCharacterEncoding(encoding);
// move on to the next
chain.doFilter(request, response);
}
-Original Message-
From: Mike Wannamaker [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2006 4:51 PM
To: 'Tomcat Users List'
Subject: URIEncoding and P
I can specify URIEncoding="UTF-8" in Tomcat's connector settings within the
server.xml file. Now, my Tomcat server correctly reads the URL GET
parameters correctly...sending out "Hello, José!" or "Hello, 田中!" as
expected.
However, there's still a problem
50 matches
Mail list logo
