Return-Path: Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 63711 invoked from network); 11 Dec 2002 22:35:35 -0000 Received: from i.meepzor.com (HELO Boron.MeepZor.Com) (204.146.167.214) by daedalus.apache.org with SMTP; 11 Dec 2002 22:35:35 -0000 Received: from Golux.Com (dmz-firewall [206.199.198.4]) by Boron.MeepZor.Com (8.11.6/8.11.6) with ESMTP id gBBMZh114124; Wed, 11 Dec 2002 17:35:43 -0500 Message-ID: <3DF7BDEB.18360838@Golux.Com> Date: Wed, 11 Dec 2002 17:36:27 -0500 From: Rodent of Unusual Size Organization: The Apache Software Foundation X-Mailer: Mozilla 4.79 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: docs@httpd.apache.org Subject: Re: Docs correction? re Auth References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Andr� Malo wrote: > > The problem is: Such an URL is illegal. It's explicitely > forbidden by RFC 1738 and RFC 2616. rfc 1738 section 3.1 defines this as a valid syntax. section 3.3 says it's not permitted in http: uris -- which is fine, since it is never(1) sent to the server. the client always(1) decomposes it into a valid http: uri and an authorization: request header field. therefore, modulo my previous message, this trick should(1) work for all semi-reasonable clients. (1) i know of *no* clients that do not handle this as described, but it's possible there are some. they would hardly be mainstream, in any case, and almost certainly batch clients rather than user-interfacine browsers. -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!"