Origin Trial token of SiignedExchange is not correctly checked after redirect |
||
Issue descriptionChrome Version: 72.0.3588.0 (Official Build) canary (64-bit) OS: All What steps will reproduce the problem? (1) Enable chrome://flags/#allow-sxg-certs-without-extension (2) Open http://bit.ly/2yvnzbX which returns a 301 redirect response with "Location: https://htxg-b1.appspot.com/sxg/hello_ec.sxg?v=" header. What is the expected result? - "https://htxg-b1.appspot.com/sxg/hello_ec.sxg?v=" returns a signed exchange with a valid Origin Trial token for "https://htxg-b1.appspot.com" - Chrome handles the returned signed exchange and shows the content of the signed exchange "Hello SignedHTTPExchange". What happens instead? - The navigation is cancelled.
,
Oct 29
c8d8e9ea12485396934020d2d6e702b0fdbc2e63 landed in 72.0.3593.0 I verified that http://bit.ly/2yvnzbX shows "Hello SignedHTTPExchange" in 72.0.3594.0. |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Oct 26