I haven’t yet had time to approve Erik’s comment myself (by trying it out) but it did some research on the web which seemed to approve it.

Furthermore I had a look at the Source code part where a comment says:

1581 // Bypass the network cache in cases where it makes no sense:
1582 // 1) Multipart responses are very large and would likely be doomed by the
1583 // cache once they grow too large, so they are not worth caching.
1584 // 2) POST responses are always unique, and we provide no API that would
1585 // allow our consumers to specify a "cache key" to access old POST
1586 // responses, so they are not worth caching.


So, when using a GET request for loading data via XHR it should indeed be cached. I will verfiy this.