search

ampproject / amphtml

The AMP web component framework.
https://amp.dev
Apache License 2.0
14.89k stars 3.89k forks source link

amp-live-list update problem with google amp cache #13659

Closed spinmar closed 4 years ago

spinmar commented 6 years ago

Hi, we have a problem in our amp live football soccer page related to google amp cache. We have the live of italian serie A and serie B football games The user can follow the live without refresh the page: in non amp page we handle it with javascript while in the amp one we use the tag amp-live-list with refresh time of 20 seconds. If the user call the amp page directly there is no problem and the refresh is working well: Example.

https://sport.virgilio.it/dirette/live/serie-a/26-2-2018/cagliari-napoli/3835/amp/

While if the user goes to the page from google search results and then from google cache it seems that the page is not refreshing.

https://www.google.it/amp/s/sport.virgilio.it/dirette/live/serie-a/26-2-2018/cagliari-napoli/3835/amp/

Our server replies always with max-age:0 and then google should not cache the page. Google should always ask the page to our server. During the live the amp version of page is always lagging behind not amp page. Can some explain me where is the problem? Thanks

xavierleune commented 5 years ago

@twifkak Ok, thanks. Do you have any advice regarding this cache-control: max-age=0, no-cache ? Can the no-cache be an issue here ? And I'm following another lead to, can a redirection be an issue ? i.e: if an article was cached on /great-article.amphtml and now redirects to /best-article.amphtml (both being valid amp pages). I feel like there is also something here. Am I wrong ?

xavierleune commented 5 years ago

@twifkak friendly ping :)

twifkak commented 5 years ago

@xavierleune Sorry for the delay!

I believe max-age=0, no-cache would be OK. I can't think of any reason redirection within the same site would be an issue; redirection to a different site might result in a different crawl budget.

We've made some experimental (partial?) improvements to the freshness of ?amp_latest_update_time= responses (i.e. requests coming from the <amp-live-list> component). Let me know whether you notice a difference.

twifkak commented 4 years ago

Closing. I've heard some feedback (offline) that this is fixed for some publishers, and I've heard no feedback that it isn't. Feel free to re-open if you have a counterexample.