Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.220.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <BANLkTin1JYo7WUQDGn0AZskRoSnocF+bYQ@mail.gmail.com>
References: <4E0B0822.5000904@kippdata.de>
	<BANLkTi=sAuZUo+FBp1cMtoTvf83eEk_i8w@mail.gmail.com>
	<BANLkTin1JYo7WUQDGn0AZskRoSnocF+bYQ@mail.gmail.com>
Date: Wed, 29 Jun 2011 20:31:29 +0400
Message-ID: <BANLkTi==9DtfukhVJ4GFhXDGRWavGCLj=w@mail.gmail.com>
Subject: Re: response.encodeURL("http://localhost:8080") produces an invalid
 URL?
From: Konstantin Kolinko <knst.kolinko@gmail.com>
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

2011/6/29 Erik Bertelsen <bertelsen.erik@gmail.com>:
> 2011/6/29 Konstantin Kolinko <knst.kolinko@gmail.com>:
>
>>
>> From HTTP standpoint it should be http://localhost:8080/ and in my
>> experience browsers add the trailing slash automatically. I have not
>> looked whether the actual HTTP spec is more strict regarding such
>> URLs.
>>
>
> Actually my experience is slightly different, i.e. the HTTP servers
> send a redirect which adds the trailing /.

Redirect is sent for  folder -> folder/, but here we are talking about
server root ('/').

For the server root the request itself should contain "/". That is
taken care by the browser: in an HTTP request, e.g.
GET / HTTP/1.0
 - the requested path cannot be empty, because multiple spaces are
treated as single one.


Best regards,
Konstantin Kolinko

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