--- Comment #2 from Tisza Gergő <> ---
The reason for using XHR is that we want to access the headers so that we know
whether the image was a cache hit on varnish, and if not, how is loading time
split between thumbnail generation and real loading. (Anecdotally, slow
rendering seems to be a big issue, with multiple-second image loading times,
but we don't now how prevalent the problem is.) On production, this would only
happen in an 1/1000 sample, not every request.

The original plan was to preload images via XHR, then set the src to the same
URL as in the XHR request, but at least in current Chrome, that causes the
image to be re-requested.

You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to