-
Maks Orlovich authored
We need to handle it in the browser for navigation redirects; which by upcoming security rules means that the network service should parse it, which requires the code to be in services/network The renderer also needs to parse it, so it needs to be in services/network/public/cpp. Also ParseAceptCH got split into ParseAcceptCH and FilterAcceptCH along the way, since it feels like network service shouldn't know about browser experiments on what hints to support. Bug: 1050726 Change-Id: I4b10ce6ddf97efd852a44d4c8a4f85a9a6a0c404 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124734 Commit-Queue: Maksim Orlovich <morlovich@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#756826}
0be148b8