[AW NS] Fix failing ClientOnReceivedError2Test tests: header is not necessarily empty.
Update the relevant failing ClientOnReceivedError2Test tests (listed below) to not check for empty headers. Request headers in onReceivedError callback may or may not be empty, this is an implementation detail. In the network service code path they may e.g. contain user agent, see https://crbug.com/893573. Also add a comment in tests explaining this. Fixed tests: -ClientOnReceivedError2Test.testIframeSubresource -ClientOnReceivedError2Test.testImageSubresource -ClientOnReceivedError2Test.testMainFrame -ClientOnReceivedError2Test.testUserGesture -ClientOnReceivedError2Test.testUserGestureForIframeSubresource BUG=893573,841556 Cq-Include-Trybots: master.tryserver.chromium.android:android_mojo Change-Id: Ic6322c7d9720b62709c2b506639108ed2a36a188 Reviewed-on: https://chromium-review.googlesource.com/c/1356801Reviewed-by:Tobias Sargeant <tobiasjs@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Commit-Queue: Tim Volodine <timvolodine@chromium.org> Cr-Commit-Position: refs/heads/master@{#612777}
Showing
Please register or sign in to comment