> > > >---- Original Message ---- >From: [EMAIL PROTECTED] >To: debian-user@lists.debian.org >Subject: Re: Issue with URL and firefox (iceweasel) >Date: Fri, 17 Oct 2008 20:12:58 +0100 > >>On Fri, 17 Oct 2008 11:27:48 +0200 >>"Mathieu Malaterre" <[EMAIL PROTECTED]> wrote: >> >>Hello Mathieu, >> >>> ok, at least I am not going nuts :) >> >>:-) >> >>After Marc Shapiro replied, I realised that my "one shot" test was >>probably not good enough so, like him, I tried several more times. >More >>often than not, I got the correct file. About 40% of the time a 404 >>error. So, I'm at a loss. Marc's theory has the beauty of it being >>something other than Debian/FF/IW at fault. >> >>> Thanks >> >>You're welcome. >> >>-- >> Regards _ >> / ) "The blindingly obvious is >> / _)rad never immediately apparent" >> >>Two sides to every story >>Public Image - Public Image Ltd
I'm wondering if it has something to do with the socket selection at the server end. Normally TCP will listen on port 80 and if a connection is requested it picks an "ephemeral" (unused, vacant, high address) port upon which to respond so that port 80 is free to answer other requests. Depending on the implementation it likely picks different ports each time depending on the load. this may account for the sporatic behavior Larry >> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
