|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Thu, 2004-04-29 at 13:55, Ralph E. Kenyon, Jr. wrote: > See if this is relevant to your situation. It helped me on my Redhat 9 > setup. That was our prior correspondence. :) The problem here is that everything works properly as long as tux is instructed to listen to http://0.0.0.0:80 As soon as I specify an IP to listen to, excluding all of the other IPs on the machine, tux does indeed answer properly on the port, but its behavior changes in that 404s are no longer passed to the backend. Reset listen to http://0.0.0.0:80, works like a champ.
[Older Fedora Users Mail] [Home] [Fedora Legacy] [Fedora Desktop] [iPod Nano] [ATA RAID] [Fedora Bible] [Fedora Marketing] [Fedora Mentors] [Fedora Packaging] [Fedora SELinux] [Big List of Linux Books] [Yosemite News] [Yosemite Photos] [KDE Users] [Fedora Tools] [Fedora Docs]