> > > > Can anyone tell me what Firefox is doing when it says it is
> > > > "Connecting" to a particular website? My site is periodically hanging
> > > > at that point, and I'd like to track down the problem. Is it just
> > > > waiting for apache2's first response to the HTTP request?
> > >
> > > No, Firefox is propably waiting for the TCP connection to be
> > > established. Use something like wireshark or tcpdump to find out for sure.
> >
> > I was trying to login (via ssh) to a virtual server and it was taking ages
(19
> > secs or so). Apparently there was something wrong with the way the sysadmin
> > had set up DNS. Once fixed I would be asked for a passwd with 1-2 seconds.
> > It could be that something like this is wrong with your server?
>
> I'll check that out. Thanks guys.
>
Try it with 'curl'
ie:
curl -v www.google.com
If it doesnt find an IP, its a DNS problem, if it finds an IP but
doesn't connect, it may be a routing problem, if it works for all
sites, but not a particular site, that site might be broken, and
'curl' might be able to help you see where.
Thanks Kent. When I'm browsing my site and it hangs, I ping the
domain and the times are normal even though I'm having trouble
connecting at the exact same time. The pings are really slow in
coming back, but the reported times are normal. Does that sound like
a problem with apache2 then?
- Grant
--
[EMAIL PROTECTED] mailing list
