GitLab

HTTP_BAD_REQUEST status needs to be special-cased, because it can be
used to distinguish inactionable (potentially transient) errors from
the case when local data is outdated and user action is required to go
out from this state.

Bug: 1113598
Change-Id: If7389a7ecf534139e7a610b1f7c8b93fdc25ce1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2526348
Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#830176}