From owner-freebsd-stable@FreeBSD.ORG Thu Jul 28 09:41:25 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D1D616A41F for ; Thu, 28 Jul 2005 09:41:25 +0000 (GMT) (envelope-from jowens@ghiapet.homeip.net) Received: from ms-smtp-04.rdc-kc.rr.com (ms-smtp-04.rdc-kc.rr.com [24.94.166.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id A911643D49 for ; Thu, 28 Jul 2005 09:41:24 +0000 (GMT) (envelope-from jowens@ghiapet.homeip.net) Received: from mycroft.ghiapet.net (CPE-69-76-111-42.wi.res.rr.com [69.76.111.42]) by ms-smtp-04.rdc-kc.rr.com (8.12.8p1/8.12.7) with ESMTP id j6S9OAwJ023818 for ; Thu, 28 Jul 2005 04:24:11 -0500 (CDT) Received: from [192.168.0.201] (mycroft.ghiapet.net [192.168.0.201] (may be forged)) by mycroft.ghiapet.net (8.13.1/8.13.1) with ESMTP id j6S9f8UY022635; Thu, 28 Jul 2005 04:41:09 -0500 Message-ID: <42E8A82E.5020801@ghiapet.homeip.net> Date: Thu, 28 Jul 2005 04:41:02 -0500 From: "John R. Owens" User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org References: <15339.62.2.21.164.1122537718.squirrel@www.gwch.net> <42E8A2DB.4070603@bmby.com> <42E89D53.5010000@ghiapet.homeip.net> <18524.62.2.21.164.1122541819.squirrel@www.gwch.net> In-Reply-To: <18524.62.2.21.164.1122541819.squirrel@www.gwch.net> X-Enigmail-Version: 0.91.0.0 OpenPGP: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig62D063E1E31B07EDEC8188C7" X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Subject: Re: Apache2 just listening to https? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jul 2005 09:41:25 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig62D063E1E31B07EDEC8188C7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Roger Grosswiler wrote: >>Uzi Klein wrote: >> >>>Roger Grosswiler wrote: >>> >>>>i did a file called virtual.conf in /usr/local/etc/apache2/Include with >>>>this content: >>>> >>>> >>>>ServerName freebsd.domain.net >>>>ServerAlias freebsd.domain.net >>>>DocumentRoot /usr/local/www/data >>>> >>>> >>>>...which should be loaded on startup. Also, i activated >>>> >>>>NameVirtualHost *:80 >>>> >>>>in httpd.conf - still no success...whats up here? firewall is open, >>>>redirecting on router is well...but still no success... >>>> >>>>:-( Roger >>> >>>Try checking it using telnet: >>> >>># telnet freebsd.domain.net 80 >>>GET / HTTP/1.1 >>>Host:freebsd.domain.net >>> >>>[ .. twice enter here .. ] >>> >>>and see if it gives you a clue >>> >>>-Uzi >> >>Technically, to be HTTP/1.1 compliant, that should be: >># telnet freebsd.domain.net 80 >>GET / HTTP/1.1 >>Host: freebsd.domain.net >>Connection: close >>[ .. twice enter here .. ] >> >>otherwise Apache should (I haven't tested, this is per the HTTP/1.1 RFC >>2616) assume a persistent connection and leave you hanging after your >>request until whatever time you have for your KeepAliveTimeout has passed. >>Also, it would be simpler to do "HEAD / HTTP/1.1" etc., so you don't get >>the content of your server root or its DirectoryIndex file. Just the >>good stuff that tells you what you want to know about the server, if >>it's responding on that port at all. >> > > i get it with telnet, but even not with elinks or lynx :-( > > Roger It's not just a clue whether it responds or not, it's _what_ it says. For instance, on my Fedora box (the FreeBSD box is remaking Apache right now), I get: HTTP/1.1 200 OK Date: Thu, 28 Jul 2005 09:19:48 GMT Server: Apache/2.0.52 (Fedora) Last-Modified: Wed, 22 Jun 2005 04:20:42 GMT ETag: "f00a6-91d-e4547a80" Accept-Ranges: bytes Content-Length: 2333 Connection: close Content-Type: text/html; charset=UTF-8 It doesn't really tell a whole lot in and of itself, but even more informative, if you have the appropriate modules and directives enabled, would be the output of "GET /server-status HTTP/1.1" and/or "GET /server-info HTTP/1.1", or the corresponding parsed output from lynx or whatever. It does help slightly to know if it's a 200 response, or a 403, 404, or whatever, even without server-info/server-status. Meanwhile, one thing you might try, get rid of the ServerAlias that's identical to the ServerName. I don't think it should be a problem, but it certainly can't help; ServerAlias is only for when the virtual host might be called by names other than the ServerName. -- John R. Owens ProofReading Markup Language: http://prml.sourceforge.net/ --------------enig62D063E1E31B07EDEC8188C7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC6Kg0i0+Id/zGcbARAvlLAJ9SNfTyzVlNXp1cflUw6ajjCewVVgCdGzJS h53sMyllpUrwg4JBg3/sTWA= =I4Pt -----END PGP SIGNATURE----- --------------enig62D063E1E31B07EDEC8188C7--