Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44EB1F35.5060403@rowe-clan.net>
Date: Tue, 22 Aug 2006 10:13:57 -0500
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
User-Agent: Thunderbird 1.5.0.5 (X11/20060808)
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: mod_proxy_ftp relative directory bug
References: <200608222126.34516.jsnow27@gatesec.net>
 <200608221545.31429.nick@webthing.com>
In-Reply-To: <200608221545.31429.nick@webthing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Nick Kew wrote:
> 
> That correction, in either http or ftp, is the business of the origin server,
> not the proxy.  For a proxy to issue it would be deeply broken.

Not really.  Consider the semantics of FTP.  FTP can serve a 'directory' with
LIST or NLST, but I'd only want that to be in response to /dir1/, not /dir1
since the later is pretty ambiguous.

But FTP has no concept of redirects, so your assertion that the FTP origin
server is responsible for a redirect is silly.  It doesn't follow web URI
conventions, so 'fitting' an FTP server into the role of a URI resource is
the job of the FTP client, or the HTTP proxy layer for an HTTP client.

I'd personally agree that if we know /dir1 is a directory resource, we should
probably teach mod_proxy_ftp to provide the /dir1/ redirect.