20463 2008-08-20 13:15:19 -0700 Safari short timeout causes many pages to fail to load 2011-02-18 10:30:02 -0800 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) Mac OS X 10.5 RESOLVED DUPLICATE 19758 P4 Normal --- 0 fabian webkit-unassigned ap mrowe oldest_to_newest 88932 0 fabian 2008-08-20 13:15:19 -0700 Backstory: Safari 1 had an annoying bug where it would timeout and fail to load pages if the server did not respond within 60 seconds. This spawned a number of third-party products which hacked a reasonable default back into safari. Eventually, safari developers realized that this was an unbelievably dumb idea and set the timeout to 1 year. Today: This timeout is back. So access to any page which, say, performs a log search, or (and this one is a real gem) uploads firmware to a router or other device, craps out at 60 seconds. If it happens to be a router you were updating, you are badly and irreversibly screwed. Thus the high priority assigned to this bug. 88959 1 mrowe 2008-08-20 15:56:35 -0700 I believe that the timeout to which you refer lives in CFNetwork, rather than WebKit, which makes this unlikely to be something that WebKit can address. 89013 2 fabian 2008-08-21 12:11:36 -0700 OK, so how does one report a bug in CFNetwork? 89048 3 mrowe 2008-08-21 18:53:46 -0700 You should file a bug report at http://bugreport.apple.com/. Including a URL that can be used to reproduce the problem will make it easier to investigate. 353653 4 ap 2011-02-18 10:30:02 -0800 *** This bug has been marked as a duplicate of bug 19758 ***