Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of covener@gmail.com designates
 66.249.92.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=DxHGo6reSzLBn8YV0vwgMZyI/DTN6CXhTm0QppuTaoEbO8exyWxHoogfpcrpUyEXIO
         451CTPcWdLExKueov+LXSWj7fh/CVGwHGbmXsXA0HAvDLmcnKcbEBuYNDzUP/4/CghYh
         Qhh0OSAkOaUxmWC+kztBaDmbdXCmACLIsMMCI=
Message-ID: <1404e5910809250444j1ccb270by74e4b20e00fdf294@mail.gmail.com>
Date: Thu, 25 Sep 2008 07:44:37 -0400
From: "Eric Covener" <covener@gmail.com>
To: users@httpd.apache.org
In-Reply-To: <b8a714240809250200x5ec98eedl8eadec1f36f28dcb@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <b8a714240809230436j366ef6d8y2af0fd301d73dfe4@mail.gmail.com>
	 <48D8FAAD.6000001@ice-sa.com>
	 <b8a714240809240152s7c6d90d3l582ca850696cca7a@mail.gmail.com>
	 <b8a714240809240159t58064acct800fac8fb63098c@mail.gmail.com>
	 <48DA9821.8060701@ice-sa.com> <48DAAEC1.3090708@rowe-clan.net>
	 <b8a714240809241508w1de447feqc40f37a3e4c8ea07@mail.gmail.com>
	 <48DB3260.1040707@ice-sa.com> <48DB4F59.4000103@ice-sa.com>
	 <b8a714240809250200x5ec98eedl8eadec1f36f28dcb@mail.gmail.com>
Subject: Re: [users@httpd] Differences between different Apaches in file
 requests

On Thu, Sep 25, 2008 at 5:00 AM, #V[=C1]lent=EDn <valentin@sanva.net> wrote=
:

>> In any case, thanks for bringing this problem up.  I have been using
>> Apache for a very long time, and I am also not an native English-speaker=
.  I
>> can't imagine that I have not encountered the same issue before, so I ca=
n
>> only imagine that this logic is relatively new in Apache under Windows.
>>

Seems to be the same behavior in 2.0, I hadn't seen anyone post the
error log entry generated for these:

(22)Invalid argument: Cannot map GET /%DE HTTP/1.1 to file

IMO this should be a decent hint to keep someone from looking at
permissions or authorization.  Net, you have to carefully link to your
non US-ASCII content on all platforms, you can't just type something
semantically equivalent in your client.


--=20
Eric Covener
covener@gmail.com

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org