Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 67534 invoked by uid 500); 18 Nov 2001 22:43:38 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 67364 invoked by uid 500); 18 Nov 2001 22:43:37 -0000 Delivered-To: apmail-new-httpd@apache.org Date: Sun, 18 Nov 2001 14:43:48 -0800 (PST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@titatovenaar.sfo.covalent.net To: dev@httpd.apache.org cc: TLOSAP Subject: Re: URL encoding hostnames In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sat, 17 Nov 2001, Marc Slemko wrote: > (offtopic, but related...) > > is "http://%77ww.apache.org/" a valid URL refering to the same resource > that "http://www.apache.org/" does? > > RFC 2616 section 3.2.3 seems to imply that, for comparison purposes, > they are the same. Though there are people who request this to be allowed - right now the syntax specified does not allow for %-encoding on the protocol and hostname part of the URI. However under the motto 'be strict in what you send; leisure in what what you accept' - I guess apache should accept it on the Host: header line. Dw