Date: Mon, 9 Jun 1997 01:01:38 -0400 (EDT) From: Dev Chanchani <dev@wopr.inetu.net> To: Bernie Doehner <bad@uhf.wireless.net> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Waiting for reply... Message-ID: <Pine.BSF.3.95q.970609005624.737A-100000@wopr.inetu.net> In-Reply-To: <Pine.BSF.3.95.970609004024.561B-100000@uhf.wdc.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Okay, I have been playing with the problem, it gets really _wierd_.. Lets say two files, works.gif and hang.gif. myserver.com>I type telnet www.myserver.com 80 GET /graphics/hang.gif <binary dump of file> another_network.com>telnet www.myserver.com 80 GET /graphics/hang.gif <server hangs> So basically, any machine on our network can retrieve the file fine, machines outside are network just cause the web server to hand.. BTW: works.gif will retrieve the file from my network and outside networks. Even if I rename the files back and forth, the original hang.gif (no matter waht the name) will not transfer if the request is outside our network. Now it gets wierd.. myserver.com> ftp myserver.com login as me put hang.gif puts into my home directory fine myserver.com> ftp anotherserver.com login as my friend put hang.gif ftp just HANGS this file will transfer between various machines in our network fine and load into the browser, etc, but not outside our network. Cannot ftp the file out either. other files (even with the same name) ftp in and out fine. The file has been republished through the graphics program, still will not transfer. Any ideas? Dev On Mon, 9 Jun 1997, Bernie Doehner wrote: > > > I run a FreeBSD 2.2.1 release server on a PPro w/64 MB of Ram with > > Server version Stronghold/1.3.4 Ben-SSL/1.3 Apache/1.1.3.. > > > Certain web requests just seem to be waiting for reply forever. It seems > > to be the same files over and over (like a small background image). I am > > doing into the same ISP where we get our link, and our bandwidth is less > > then 10% utilized. Anyone know what could be causing this? > > > > Not sure if this is related, but regardless, you should upgrade to Apache > 1.2. > > Many security/performance improvements. Try upgrading and see if it fixes > your problem. > > Bernie > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970609005624.737A-100000>