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: >>>> >>>><VirtualHost *:80> >>>>ServerName freebsd.domain.net >>>>ServerAlias freebsd.domain.net >>>>DocumentRoot /usr/local/www/data >>>></VirtualHost> >>>> >>>>...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/
signature.asc
Description: OpenPGP digital signature
