[Webkit-unassigned] [Bug 14539] Safari randomly can't load pages anymore

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Jul 8 11:42:43 PDT 2007


------- Comment #7 from y.kalter at home.nl  2007-07-08 11:42 PDT -------
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > In the summary, you said it doesn't work "anymore".  When did it stop working? 
> > > Where there any major changes when it stopped working (like a change of ISP, or
> > > new network hardware)?
> > 
> > When I first bought my iMac, in February, i already had this wireless network.
> > I use an updated Linksys WRT54G v2.2 router. Also, I haven't changed ISP since.
> What I was trying to determine is if something changed (in the past) that
> caused the images to stop loading properly.  Did images always load properly
> before you bought your iMac?  When did they stop working?

Everything worked great before I bought the Macs. My dad still has an Asus
notebook running XP SP2 and it never has this problem. Also, if I use Firefox I
don't have this problem on both Macs. 

> > > If you bypass your wireless router (e.g., use a wired connection directly),
> > > does that ever exhibit the issue?
> > 
> > I'm going to try that today, I will report back on that later.
> Great!

I can't seem to reproduce this problem when running on a wired connection, but
the problem was hard to trigger today. I will try it a bit more tommorow.

> > > Do you know if your ISP has an transparent HTTP proxy being used upstream from
> > > you?
> > 
> > Sorry, I don't know. Any way I could see that?
> Looking at the output of "curl -I URL" may give some clues.  For example, this
> is what I see on my network, but if you have slightly different headers, that
> means there could be a proxy involved:

Here is my output:
$ curl -I http://tweakers.net
HTTP/1.1 200 OK
Date: Sun, 08 Jul 2007 18:03:25 GMT
Server: Apache/2.2.3 (Debian)
Expires: Mon, 26 Jul 1995 05:00:00 GMT
Last-Modified: Sun, 08 Jul 2007 18:03:25 GMT
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: pre-check=0, post-check=0, max-age=0
Pragma: no-cache
Set-Cookie: TnetID=ea9e118392151de82cc78e3f4a9ed0d7; expires=Thu, 31-Dec-2037
23:00:00 GMT; path=/; domain=.tweakers.net
Set-Cookie: tc=1183917805%2C1183917805; expires=Tue, 07-Aug-2007 18:03:25 GMT;
path=/; domain=.tweakers.net
Set-Cookie: channel=main; expires=Mon, 07-Jul-2008 18:03:25 GMT; path=/;
Connection: close
Content-Type: text/html; charset=ISO-8859-15

> > Also, I'm sorry if this isn't a Safari/WebKit bug, but this problem is so hard
> > to find a solution for.
> It's much easier to diagnose issues through Bugzilla, then put them in Radar
> (Apple's internal bug tracker) when sufficient information has been found. 
> Since this issue directly affects your browsing experience on Safari, it's okay
> to explore the issue here.
> The best thing to do may be to capture a packet trace when pages aren't loading
> properly using the "tcpdump" command.  Here's how:

I let that command run and opened up Safari. I let it load a thread (with many
images) on the Tweakers.net forum (got.tweakers.net) and it locked up. I
attached the packets.tcpdump file above.

Thank you for your help so far.

Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list