EventSource should reestablish the connection when servers responded 500 error.
Reported by
star.c...@gmail.com,
May 13 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.47 Safari/537.36 Steps to reproduce the problem: 1. Create an EventSource instance with a valid URL. 2. A server at the URL responds 500 error. Repro code: https://github.com/mysticatea/event-source-500 What is the expected behavior? EventSource tries to reestablish the connection because the specification says: > HTTP 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway Timeout responses, and any network error that prevents the connection from being established in the first place (e.g. DNS errors), must cause the user agent to asynchronously reestablish the connection. > > http://www.w3.org/TR/eventsource/#processing-model What went wrong? The connection of EventSource was not reestablished. Did this work before? No Chrome version: 59.0.3071.47 Channel: beta OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: There was the issue ( https://bugs.chromium.org/p/chromium/issues/detail?id=453211) but it was archived.
,
May 15 2017
,
May 16 2017
,
May 18 2017
,
May 18 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 21 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ranjitkan@chromium.org
, May 15 2017