GitLab

Before this patch, Chrome always set Sec-Fetch-Site header to
"cross-origin" when downloading manifests to verify Android payment
apps.

This patch sets the initiator origin for downloading payment method
manifest files and sets that file's origin as the initiator of web app
manifest file download when verifying Android payment apps. These
origins enable setting the correct Sec-Fetch-Site headers in network
request, for example.

In addition, this patch uses org.chromium.url.URI objects in the JNI
interface of PaymentManifestDownloader.java instead of converting to and
from a string.

After this patch, Chrome correctly sets Sec-Fetch-Site header to either
"cross-origin", "same-site", or "same-origin" when downloading manifests
to verify Android payment app.

Bug: 1048201
Change-Id: If256926daa4a9e43733d79c8fd3049cfbd65a5c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2044710
Auto-Submit: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Sahel Sharify <sahel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#740352}