Re: Issue with URL and firefox (iceweasel)
On Fri, Oct 17, 2008 at 18:26:57 -0700, owens@netptc.net (owens@netptc.net) wrote:
> 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
As noted elsewhere in this thread, port 50043 was what I was seeing in
the failure message, so perhaps this is a good theory of yours.
--
Bob Cox. Stoke Gifford, near Bristol, UK.
Registered user #445000 with the Linux Counter - http://counter.li.org/
Reply to: