From owner-freebsd-bugs Mon Sep 25 7:50:10 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E05F237B42C for ; Mon, 25 Sep 2000 07:50:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id HAA32926; Mon, 25 Sep 2000 07:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 25 Sep 2000 07:50:02 -0700 (PDT) Message-Id: <200009251450.HAA32926@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ruslan Ermilov Subject: Re: bin/21476: ftp in 4.1-STABLE fails on http:// URLs Reply-To: Ruslan Ermilov Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/21476; it has been noted by GNATS. From: Ruslan Ermilov To: Dag-Erling Smorgrav Cc: bug-followup@FreeBSD.org Subject: Re: bin/21476: ftp in 4.1-STABLE fails on http:// URLs Date: Mon, 25 Sep 2000 17:42:24 +0300 On Mon, Sep 25, 2000 at 04:23:08PM +0200, Dag-Erling Smorgrav wrote: > Ruslan Ermilov writes: > > Forgive me my ignorance but from where of the above it does follow that > > the HTTP/1.0 request should include the Host: header and not having it > > there should be answered with a 404 reply? For example, > > Read section 19.6.1.1 of RFC2616. Pay special attention to the part > that says "including updates to existing HTTP/1.0 applications" and > the part that says "Both clients and servers MUST support the Host > request-header". > > Or just forget the RFC and consider that if ftp(1) does not send a > Host: header, it simply will not work with the thousands if not > millions of web sites out there that are actually virtual hosts. > This is the case here -- the server does a virtual hosting and returns 404 because either the "default" virtual host does not have this document or there is no "default" virtual host at all. > Regarding the fact that not sending a Host: header sometimes works, > and sometimes doesn't, even on servers that host a single site - this > is a consequence of Apache striving to be backwards compatible wrt the > format of its configuration file (to be more specific, there are two > different ways to configure a single-site server, and one of them > causes requests without a Host: header to fail) > It is actually because RFC does not say that the HTTP/1.0 request without a Host: header MUST be answered with a 400 error. It may, however, be answered with a 404 error (like in this particular case). Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message