Return-Path: 
 <users-return-212362-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 66665 invoked from network); 18 May 2010 08:19:30 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 18 May 2010 08:19:30 -0000
Received: (qmail 84368 invoked by uid 500); 18 May 2010 08:19:26 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 84088 invoked by uid 500); 18 May 2010 08:19:26 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 84079 invoked by uid 99); 18 May 2010 08:19:26 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 May 2010 08:19:26 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates
 212.85.38.228 as permitted sender)
Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 May 2010 08:19:19 +0000
Received: from localhost (localhost [127.0.0.1])
	by tor.combios.es (Postfix) with ESMTP id 1668C226193
	for <users@tomcat.apache.org>; Tue, 18 May 2010 10:18:05 +0200 (CEST)
Received: from tor.combios.es ([127.0.0.1])
	by localhost (tor.combios.es [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zM4PKL1E5Ql7 for <users@tomcat.apache.org>;
	Tue, 18 May 2010 10:18:05 +0200 (CEST)
Received: from [192.168.245.129] (p549EA712.dip0.t-ipconnect.de
 [84.158.167.18])
	by tor.combios.es (Postfix) with ESMTPA id BDCBC226177
	for <users@tomcat.apache.org>; Tue, 18 May 2010 10:18:04 +0200 (CEST)
Message-ID: <4BF24D64.2070005@ice-sa.com>
Date: Tue, 18 May 2010 10:18:44 +0200
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
Reply-To: Tomcat Users List <users@tomcat.apache.org>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: =?ISO-8859-1?Q?Re=3A_Problem_using_=22response=2EsendRedir?=
 =?ISO-8859-1?Q?ect=22_to_redirect_to_URL_that_includes_=22?=
 =?ISO-8859-1?Q?=F1=22_or_tilde?=
References: 
 <7E9C5E91EA957B4AA237D57A011BA6110135197E@TSEBCNMAILCLU.itc.ads.t-systems.es>
In-Reply-To: 
 <7E9C5E91EA957B4AA237D57A011BA6110135197E@TSEBCNMAILCLU.itc.ads.t-systems.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked by ClamAV on apache.org

Perez Manglano, Moises wrote:
> I�ve found an alternative solution for "�" issue; instead of redirect using "response.sendRedirect", i�ve used the HTML META tag in this way:
> 
> <meta content="0;URL=http://www.coru�a.es" http-equiv="refresh">
> 
> It redirects to the correct URL properly.
> 
Good if this resolves your current issue.
I just want to point out that it is not strictly equivalent, and less 
efficient internet-wise.
As I understand the matter, the above solution is not equivalent to a 
302 or 301 redirect, because it will not cause the browser to "remember" 
that this document is now somewhere else.  The browsers will thus 
continue to request the original URL, obtain it, and then immediately 
"refresh" this page from another URL.

And it does not solve the issue of links to such hosts, embedded in a 
page.  Maybe browsers are smart enough to figure that out though.

The link provided earlier by Konstantin
http://en.wikipedia.org/wiki/Internationalized_domain_name
points to the real solution for the time being.
(see also http://en.wikipedia.org/wiki/Punycode).

However, I personally find Punycode rather "bizarre", and I am not sure 
what software is available to make this easy to handle, in Tomcat or 
elsewhere.
Among other bizarre things, it does mean that in a URL, one has to 
encode the hostname using one method, and the rest of the URL using 
another method.  As if encoding issues were not already complicated enough.

This, and a lot of other non-USASCII encoding issues all through the 
web, point to the real need to move to a fully Unicode/UTF-8 based web 
infrastructure.  It rather puzzles me why this does not seem to be a 
major topic of discussion in forums such as this one.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org