Bug 70112
| Summary: | REGRESSION (r94242): EventSource should not try to reconnect if connection establishment fails | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Per-Erik Brodin <per-erik.brodin> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | adam.bergkvist, ap, ian |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 61862 | ||
| Bug Blocks: | |||
Per-Erik Brodin
According to the specification, EventSource should not try to reconnect if it fails to establish the connection in the first place.
"any network error that prevents the HTTP connection from being established in the first place (e.g. DNS errors), must cause the user agent to fail the connection"
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ian 'Hixie' Hickson
(The idea being to avoid hammering an already suffering network.)
Per-Erik Brodin
More easily tested with CORS support.
Per-Erik Brodin
Since the spec changed, this regression is now compliant!
Alexey Proskuryakov
I'm confused. Is it now OK to keep hitting the server indefinitely, wasting bandwidth? This seems like horrible behavior if so.