...
- In Firefox, the page loads, but hangs for 20s. Another hit, another 20 second hang.
- In Chrome (64.0 tested), the page loads, but hangs for 20s. On the second hit things get interesting:
Corruption! On a third hit, more corruption, but now there is no hang:
On the second and third hit, if you view to see the state of Chrome's cache, you'll see that the page is flagged as truncated:
After the third hit, Chrome has marked the corrupt cache entry as valid:
and henceforth all requests for the URL will serve binary gibberish at the end.
This unfortunate behaviour appears to be a Chrome bug (edit: now filed as Issue 423318). Searching for RESPONSE_INFO_TRUNCATED will bring up relevant hits, including a stale bug report (https://bugs.chromium.org/p/chromium/issues/detail?id=423318) and people complaining of the same behaviour (https://stackoverflow.com/questions/47311027/response-info-truncated-file-in-chrome-cache). I am not sure what effect this binary corruption has on browsers. Possibly none, as browsers are built to handle any rubbish thrown at them.
...