[Webkit-unassigned] [Bug 14539] Safari randomly can't load pages anymore
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun Jul 8 08:59:45 PDT 2007
------- Comment #6 from ddkilzer at webkit.org 2007-07-08 08:59 PDT -------
(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?
> > 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.
> > 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:
$ curl -I http://tweakers.net/
HTTP/1.1 200 OK
Date: Sun, 08 Jul 2007 15:34:44 GMT
Server: Apache/2.2.3 (Debian)
Expires: Mon, 26 Jul 1995 05:00:00 GMT
Last-Modified: Sun, 08 Jul 2007 15:34:44 GMT
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: pre-check=0, post-check=0, max-age=0
P3P: CP="CUR ADM OUR NOR STA NID"
Set-Cookie: TnetID=46d844139cfb1f6671094f22eb00c113; expires=Thu, 31-Dec-2037
23:00:00 GMT; path=/; domain=.tweakers.net
Set-Cookie: tc=1183908884%2C1183908884; expires=Tue, 07-Aug-2007 15:34:44 GMT;
Set-Cookie: channel=main; expires=Mon, 07-Jul-2008 15:34:44 GMT; path=/;
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:
1. Open a "Terminal" window.
2. Run the "/sbin/ifconfig" command.
3. Note all of the "enX" interfaces listed. ("en0" is usually your wired
ethernet, while "en1" is usually wireless, but it's not necessarily that way.
The active interface will have a line that begins with "inet" and a valid IP
4. Wait for the page loading issues to start.
5. When they do start, run this command from the Terminal (where "en1" is the
interface you're using):
sudo tcpdump -s 0 -w packets.tcpdump -i en1
6. Type your account's password (assuming your account also has admin
7. Try loading a web page or two from Safari. (Hopefully they will fail out.)
8. Hit Ctrl-C to end the command. The tcpdump command should say that it
captured more than zero packets. If it didn't, then you either (most likely)
have the wrong interface or no packets are being sent. Try rerunning the
command with the other interface and loading more web pages.
9. Attach packets.tcpdump to this bug.
- DO NOT try to log into a web site while capturing packets, or your username
and password will be visible in the clear.
- Do not test SSL (https) web sites when capturing packets as this will make it
much more difficult to diagnose any issues.
- It would be GREAT if you could start capturing packets for a period in which
web pages are loading correctly, then suddenly stop working. This would give
the most information about the issue.
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