Bug 20463
| Summary: | Safari short timeout causes many pages to fail to load | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Fabian Mailinator <fabian> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ap, mrowe |
| Priority: | P4 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.5 | ||
Fabian Mailinator
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mark Rowe (bdash)
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.
Fabian Mailinator
OK, so how does one report a bug in CFNetwork?
Mark Rowe (bdash)
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.
Alexey Proskuryakov
*** This bug has been marked as a duplicate of bug 19758 ***