Network Error Logging: Handle ERR_EMPTY_RESPONSE |
||
Issue descriptionERR_EMPTY_RESPONSE is easy to generate in unittests, and would naturally map to "http.response.empty". I should add it to the whitelist/map of errors that NEL uses.
,
Dec 8 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a28dcb986967a86b49741b9402b6af364876db45 commit a28dcb986967a86b49741b9402b6af364876db45 Author: Julia Tuttle <juliatuttle@chromium.org> Date: Fri Dec 08 21:45:21 2017 NEL: Add ERR_EMPTY_RESPONSE -> "http.response.empty" Add ERR_EMPTY_RESPONSE to the list of errors NEL can report, since it's easy to cause in unittests with EmbeddedTestServer. Bug: 792972 Change-Id: Ic3a2cd6018ab18a1ad4b5a9d0c51e4bbf7f1ef5e Reviewed-on: https://chromium-review.googlesource.com/814755 Reviewed-by: Miriam Gershenson <mgersh@chromium.org> Commit-Queue: Julia Tuttle <juliatuttle@chromium.org> Cr-Commit-Position: refs/heads/master@{#522887} [modify] https://crrev.com/a28dcb986967a86b49741b9402b6af364876db45/net/network_error_logging/network_error_logging_service.cc
,
Dec 12 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by juliatut...@chromium.org
, Dec 7 2017