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)
From: Jon Snow <jsnow27@gatesec.net>
Reply-To: jsnow27@gatesec.net
To: dev@httpd.apache.org
Subject: mod_proxy_ftp BASE REF
Date: Tue, 9 Aug 2005 19:03:37 +1000
User-Agent: KMail/1.5.4
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200508091903.39111.jsnow27@gatesec.net>


Does anyone have any idea why/whether the BASE HREF is required in the 
proxy_ftp html code returned to the client? I would like to remove it as it is 
breaking relative links for my client's browsers that are not using an 
Authorization header. I have not found anywhere in the RFCs where it is 
stipulated as a must for the BASE HREF or that browsers must use the 
authorization header for requests subsequent to the initial authorization 
using the user:password combination in the URL. e.g. ftp://
user:password@ftp.example.com.

Thanks,
Jon