From owner-freebsd-bugs Mon Sep 25 9:30: 5 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 B5D7337B440 for ; Mon, 25 Sep 2000 09:30:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA79797; Mon, 25 Sep 2000 09:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 25 Sep 2000 09:30:02 -0700 (PDT) Message-Id: <200009251630.JAA79797@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Dag-Erling Smorgrav Subject: Re: bin/21476: ftp in 4.1-STABLE fails on http:// URLs Reply-To: Dag-Erling Smorgrav 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: Dag-Erling Smorgrav To: Ruslan Ermilov Cc: bug-followup@FreeBSD.org Subject: Re: bin/21476: ftp in 4.1-STABLE fails on http:// URLs Date: 25 Sep 2000 18:21:42 +0200 Ruslan Ermilov writes: > 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). The bottom line being that your claim that Apache was not standards- conforming was not correct in this case. Regarding the PR, I'd suggest that the originator considered using fetch(1) instead of ftp(1) for HTTP as well as for simple, non-interactive FTP requests. I'd also like to suggest that the URL functionality and the HTTP code be ripped out of ftp(1), but I'd probably ble flamed to hell and back by all the armchair generals out there, so I won't. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message