SignedExchange: if fallback URL = outer URL, then ERR_TOO_MANY_REDIRECTS |
||
Issue descriptionChrome Version: 71.0.3554.4 (Official Build) dev (64-bit) OS: Linux What steps will reproduce the problem? (1) enable SignedHTTPExchange feature (2) open devtools and click Preserve log (3) load an invalid SXG where inner URL = outer URL What is the expected result? Network error page. What happens instead? Network error page, but only after the browser goes into a redirect loop, reloading the SXG URL a bunch of times. Redirect should probably be avoided if inner URL = outer URL.
,
Sep 25
Created a repro: https://sxg-test.appspot.com/sxg/fallback_to_outer_url.sxg Current behavior is consistent with what happens when normal webpage has a redirect loop. Is there any legitimate use cases of fallback URL = outer URL ? If so, we may want to detect that and show a developer-friendly console message.
,
Dec 4
,
Dec 4
Oh, sorry I missed this question. For the Google Search SXG case, the initial implementation will require that fallback URL = outer URL (this is for a few different reasons, including: eliminating double-fetch [in error case and in AMP-first case], and signal-forwarding). These won't be served to user agents as such -- those will come from the Google cache and thus have a different outer and inner URL. However: inner = outer will be served to crawlers that send the appropriate request headers, and web developers may configure their browsers to send those request headers in order to test. For example, see the "add a Chrome extension" sentence in https://github.com/ampproject/amppackager#productionizing. Hope that helps with prioritization. |
||
►
Sign in to add a comment |
||
Comment 1 by twif...@google.com
, Sep 24