different content displayed on refresh, sometimes

Try this page: https://crates.io/crates/linked-hash-map
Sometimes you see this:

sometimes this:

simply by refreshing the (same) page (ie. F5)

This seems to be true for any package page, eg.
here's another:
https://crates.io/crates/okofdb

hmm that doesn't happen on firefox. On Firefox the first page is briefly shown then replaced by the second page in like 1 second.

Looks like, when it does display the right page(second screenshot, that is) in Chromium, it does it the same as in firefox, but a bit faster, of course.

I can't see any difference in DevTools(chromium), between the two screenshots.

local/ungoogled-chromium 77.0.3865.121_r803271.ca6b7b144491-1
local/firefox-hg r495792+.cb9bbf38fa45+-1

[smarnach]

I can't reproduce this issue in any of my browsers (Firefox, Chromium, Chrome).

Can you reproduce the issue with the "Network" tab of the developer tools open? If so, does the list of requests include https://crates.io/api/v1/crates/linked-hash-map/0.5.2/readme with a 302 status code, and https://static.crates.io/readmes/linked-hash-map/linked-hash-map-0.5.2.html with a 200 status code? Are there any error messages in the JavaScript console?

Thanks for the great ideas,
I've got a (pending) on the html, and it must then, clearly, be Chromium's fault. Just wish I knew why/how. But since I'm using some ungoogled-chromium patches and some of my own, they must be it. So closing as my bad.

good:

bad:

But note that it only happens sometimes, but I assume you've tried multiple times? (like 10 should do, with shift+LMB on the Refresh button)

if I do shift+refresh after a while, the old request gets cancelled (shows 13.8min):

the request when it fails looks like:

and when it succeeds looks like:

[smarnach]

I tried many times, and could not reproduce this on Chromium. And this indeed looks like your browser doesn't even finish sending the request, so there is nothing we can do on the crates.io end. The rendered readme files are stored on AWS S3, and served via AWS CloudFront, so this request isn't even sent to a server we control.