Currently, error page (ERR_INVALID_SIGNED_EXCHANGE) is shown in the following situations:
1. sxg header parse error
2. sxg version mismatch
3. cert fetch failure
4. cert parse failure
5. cert verification failure
6. signature verification failure
For 3-6, we should redirect to the signed exchange's request URL instead of showing an error.
(Note: we shouldn't do it for sxg prefetch.)
Once https://github.com/WICG/webpackage/issues/242 is resolved, we would be able to do it for 2. (version mismatch) too.
Comment 1 by kinuko@chromium.org
, Aug 15