Bug 26514
| Summary: | [GTK] Replaces partially loaded page with fallback content when server drops connection prematurely | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Gustavo Noronha (kov) <gustavo> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | bugs-noreply, cgarcia, jmalonzo, mrobinson |
| Priority: | P2 | Keywords: | Gtk |
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | All | ||
Gustavo Noronha (kov)
My Internet connection currently sucks, so it is common for me to have packet loss. When that happens, some servers are not very forgiving, and drop the connection before the content is fully retrieved. dev.w3.org is one such server.
When that happens, WebKitGTK+ currently replaces the already loaded content with the 'Connection terminated unexpectedly' error page. Chromium and Iceweasel both keep displaying the content they have already received.
I see two solutions here: we should keep displaying the content, but also display a warning that the content has been only partially loaded, or we should keep displaying the content as if it was the whole thing. I'm pretty sure I remember reading something about this in the HTTP spec, somewhere.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Martin Robinson
I agree! It's worth ensuring that the default signal handlers in WebKit2 obey this rule.