There seems to be some strangeness in the way that mobile-html responses are cached. (unless I'm misunderstanding something)
When I make edits, they are not always reflected right away when I get the mobile-html contents again. But I can't figure out for which types of articles this is happening
Here are the steps that I'm taking:
- In a console, make a request to fetch a mobile-html page, e.g.:
curl -I https://en.wikipedia.org/api/rest_v1/page/mobile-html/Steve_Harrington
- Observe the age header returned in the response.
- Make an edit to that page in a browser window.
- In the console, make the curl request again.
- Observe that it's still returning the old content, with a cache status of hit-front and the age increasing. It also seems to be served by the same restbaseXXX server every time, no matter how many times I repeat the request.
This is manifesting itself in the Android app as not being able to see recently-made edits, regardless of how many times we refresh.
What could be going on? Initially I thought it might be an issue with articles with a space/underscore in the name, but other similar articles work differently, such as Star_Trek, where the cache status is nearly always pass, and occasionally hit-local.