On Thu, 19 Dec 2002, CM Hood wrote: > Why do directory listing calls to the web server fail when not ending in > "/" when routed through the fire wall? The same calls by computers > behind the the firewall (not routed through the firewall) are handled > without error. > > The directory listings are self created by the web server (xitami) so I > cannot just edit all my web pages to add the extra "/". > > This only just now came up because I recently created a Bearing v1.0 > firewall/router to permit moving my web server "behind" the firewall > rather than be "in" the firewall. The firewall software used then the > web server was in the firewall was the same "Shorewall' system. > > This seams like a "Shorewall" question rather than a "Bering" item but > Shorewall recommends that these questions start here.
Smart Tom. :) > Has anyone else noticed this? Is there something I should try to make > the problem go away? This is a problem with your web server configuration. The basic mechanism is discussed many places, but [1] came up first when I googled. You need to make sure that the web server represents itself using the public address rather than the private one. For example the client might see: $ telnet somesite.com 80 Trying 217.160.111.64... Connected to somesite.com. Escape character is '^]'. * GET /hng HTTP/1.1 Connection: Keep-Alive User-Agent: Mozilla/5.0 (compatible; Konqueror/2.2.2; Linux) Accept: text/*, image/jpeg, image/png, image/*, */* Accept-Encoding: x-gzip, gzip, identity Accept-Charset: Any, utf-8, * Accept-Language: en * Host: somesite.com - HTTP/1.0 301 Moved Permanently - Date: Thu, 19 Dec 2002 23:01:17 GMT - Server: Apache/1.3.27 (Unix) mod_perl/1.27 PHP/4.2.3 + Location: http://somesite.com/hng/ - Content-Type: text/html; charset=iso-8859-1 - Connection: close Where the asterisks show the broken url you specified, and the "-" shows data returned from the web server, and "+" shows that the web server had to figure out its own public name somehow. In this case, you need to tell it to use your external hostname rather than the one it normally extracts from the OS. For Apache, I think a "ServerName" directive in a virtual host block should take care of this. [1] http://www.netmechanic.com/news/vol4/load_no11.htm --------------------------------------------------------------------------- Jeff Newmiller The ..... ..... Go Live... DCN:<[EMAIL PROTECTED]> Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/Batteries O.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --------------------------------------------------------------------------- ------------------------------------------------------- This SF.NET email is sponsored by: Geek Gift Procrastinating? Get the perfect geek gift now! Before the Holidays pass you by. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
