www.google.nl - Page does not loads as AMP page

[webcompat-bot]

URL: https://www.google.nl/amp/s/amp.theguardian.com/world/2022/jan/22/china-hires-western-tiktokers-to-polish-its-image-during-2022-winter-olympics

Browser / Version: Firefox 98.0 Operating System: Android Tested Another Browser: Yes Other

Problem type: Something else Description: The page doesn't load, I actually end up on a favicon file Steps to Reproduce: I found this page shared on social media and I tried to visit it on Firefox release and Nightly on Android.

I end up on https://static.guim.co.uk/images/favicon-32x32.ico instead.

The same issue appears on Firefox on desktop and weirdly, on Chromium on desktop.

The page works fine on Brave for Android.

Browser Configuration

• None

From webcompat.com with ❤️

[yoasif]

Also seeing this behavior on https://www.google.no/amp/s/amp.theguardian.com/world/2022/jan/21/taliban-delegation-travel-to-norway-for-human-rights-talks

[softvision-oana-arbuzov]

Thanks for the report, I was able to reproduce the issue. A favicon is displayed instead of Amp page.

Note:

1. The issue is not reproducible on Chrome and Opera.
2. Might be similar to #97516

Tested with: Browser / Version: Firefox Nightly 98.0a1 (🦎 98.0a1-20220125100058) Operating System: Google Pixel 5 (Android 12) - 1080 x 2340 pixels, 19.5:9 ratio (~432 ppi density), Samsung Galaxy S8 (Android 9) - 1440 x 2960 pixels, 18.5:9 ratio (~570 ppi density)

Moving to Needsdiagnosis for further investigation.

[qa_04/2022]

[karlcow]

Redirected to the favicon.

HTTP/2 302 Found
location: https://static.guim.co.uk/images/favicon-32x32.ico
cache-control: private
x-robots-tag: noindex
content-type: text/html; charset=UTF-8
p3p: CP="This is not a P3P policy! See g.co/p3phelp for more info."
date: Mon, 31 Jan 2022 21:49:21 GMT
server: gws
content-length: 247
x-xss-protection: 0
x-frame-options: SAMEORIGIN
set-cookie: 1P_JAR=2022-01-31-21; expires=Wed, 02-Mar-2022 21:49:21 GMT; path=/; domain=.google.nl; Secure; SameSite=none
NID=511=CElTCuGqXu3Jtn0OpmBNw2GEq_E9PWVX9kiLoL7Xe5ERYF4z_5z-RjhNM3WoAiEVizCCGtEsiqPjV-62atS9v1andV30D_yqPdxUN8WAG_jx8VkM0TitKkTWshRJCX5W-C92D9d3r1fXawSbrjAj450azSOri2I09xLr0JC8_RI; expires=Tue, 02-Aug-2022 21:49:21 GMT; path=/; domain=.google.nl; Secure; HttpOnly; SameSite=none
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
X-Firefox-Spdy: h2

[karlcow]

The reporter is saying that this is happening on chromium too. That doesn't seem a webcompat issue, but more a misconfiguration of the google servers. Let's contact them.

[karlcow]

I have contacted Google.