Received: by 10.205.127.148 with SMTP id ha20mr3048789bkc.6.1321545616163;
        Thu, 17 Nov 2011 08:00:16 -0800 (PST)
X-BeenThere: mojolicious@googlegroups.com
Received: by 10.204.152.154 with SMTP id g26ls5647550bkw.3.gmail; Thu, 17 Nov
 2011 08:00:07 -0800 (PST)
Received: by 10.204.143.143 with SMTP id v15mr5548616bku.1.1321545605089;
        Thu, 17 Nov 2011 08:00:05 -0800 (PST)
Received: by 10.204.143.143 with SMTP id v15mr5548614bku.1.1321545605071;
        Thu, 17 Nov 2011 08:00:05 -0800 (PST)
Return-Path: <kra...@googlemail.com>
Received: from mail-bw0-f52.google.com (mail-bw0-f52.google.com [209.85.214.52])
        by gmr-mx.google.com with ESMTPS id j1si5443723bky.2.2011.11.17.08.00.05
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 17 Nov 2011 08:00:05 -0800 (PST)
Received-SPF: pass (google.com: domain of kra...@googlemail.com designates 209.85.214.52 as permitted sender) client-ip=209.85.214.52;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of kra...@googlemail.com designates 209.85.214.52 as permitted sender) smtp.mail=kra...@googlemail.com; dkim=pass (test mode) header...@googlemail.com
Received: by bkas6 with SMTP id s6so3754208bka.39
        for <mojolicious@googlegroups.com>; Thu, 17 Nov 2011 08:00:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=gamma;
        h=date:from:to:message-id:in-reply-to:references:subject:x-mailer
         :mime-version:content-type;
        bh=hu9TWjmyUo3KfeH1pfvROHoIl5NF97OLa7lLEj1mA4g=;
        b=Gzw8TpQxtWYoxrfMHlNPL9D+3pZ2gecKSmQdyxoRhekJlL6BL63z5D2u4Wd2x2n31W
         iB1+E4upUWePYEk7fvHEEV3GHSeDHCMU2IwLw0BKPFaPT4nTF+bWcRxd3zLUgknGrScn
         uzPl4Cx0DuhlyysUJxZ5n8F7TIeTzqipJt99Q=
Received: by 10.204.157.154 with SMTP id b26mr27064504bkx.52.1321545604845;
        Thu, 17 Nov 2011 08:00:04 -0800 (PST)
Return-Path: <kra...@googlemail.com>
Received: from odyssey.local (p5B3CAF72.dip.t-dialin.net. [91.60.175.114])
        by mx.google.com with ESMTPS id f14sm19056074bkv.3.2011.11.17.08.00.03
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 17 Nov 2011 08:00:04 -0800 (PST)
Date: Thu, 17 Nov 2011 17:00:02 +0100
From: Sebastian Riedel <kra...@googlemail.com>
To: mojolicious@googlegroups.com
Message-ID: <A4A9FF200B6B442E985BF80BC8DB3...@gmail.com>
In-Reply-To: <alpine.DEB.2.02.1111171623010.15...@engelberg.oetiker.ch>
References: <4EB977AE.4090...@bykov.odessa.ua>
 <CAPE9xSNN4s=OsnsG8fR5eCGrCp4C6BAjcADCV3LMP5k+1bu...@mail.gmail.com>
 <alpine.DEB.2.02.1111171357220.15...@engelberg.oetiker.ch>
 <CAPE9xSPXsDjD0Zry9xbSNLaMkwvLbpD4MpDqiFdTTd7N86e...@mail.gmail.com>
 <1b10ba6e-a7ae-42b6-bf19-58a6d92cd...@m7g2000vbc.googlegroups.com>
 <alpine.DEB.2.02.1111171454010.15...@engelberg.oetiker.ch>
 <74BFA8B1A471471984DE7026DCCD5...@gmail.com>
 <alpine.DEB.2.02.1111171607240.15...@engelberg.oetiker.ch>
 <CB1CD5AF6574455893C63E79FA34C...@gmail.com>
 <alpine.DEB.2.02.1111171623010.15...@engelberg.oetiker.ch>
Subject: Re: [Mojolicious] Re: URL Root (or prefix)
X-Mailer: sparrow 1.4.2 (build 959.4)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4ec52f82_7644a45c_15585"

--4ec52f82_7644a45c_15585
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

> In the absence of SCRIPT_URI I would say the behaviour is correct.
> If SCRIPT_URI is present, then there is room for improvement, as
> Mojo is actually exposing internal information of the web server
> (the name of the script) where this could be prevented.
> 
> but a proof ... difficult :-)

Ok, then they are at least incomplete, i'll remove them for now.

  https://github.com/kraih/mojo/commit/7f7c382b7196db23bd432a99c574cbacd0e6d285

-- 
Sebastian Riedel
http://twitter.com/kraih
http://mojolicio.us
--4ec52f82_7644a45c_15585
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<blockquote type=3D=22cite=22 style=3D=22border-left-style:solid;border-w=
idth:1px;margin-left:0px;padding-left:10px;=22><span><div><div><div>In th=
e absence of SCRIPT=5FURI I would say the behaviour is correct.</div><div=
>If SCRIPT=5FURI is present, then there is room for improvement, as</div>=
<div>Mojo is actually exposing internal information of the web server</di=
v><div>(the name of the script) where this could be prevented.</div><div>=
<br></div><div>but a proof ... difficult :-)</div></div></div></span></bl=
ockquote><div><br></div><div>Ok, then they are at least incomplete, i'll =
remove them for now.</div><div><br></div><div>&nbsp; https://github.com/k=
raih/mojo/commit/7f7c382b7196db23bd432a99c574cbacd0e6d285</div><div><br><=
/div><div>--&nbsp;<br>Sebastian Riedel<div>http://twitter.com/kraih<br>ht=
tp://mojolicio.us</div></div>
            
--4ec52f82_7644a45c_15585--