XHR/fetch don't use the HTTP/2 push cache

Issue #12142852 • Assigned to AA


Jake A.
May 26, 2017
This issue is public.
Found in
  • Microsoft Edge
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

Scrappy test: https://github.com/jakearchibald/http2-push-test
Video of results: https://www.youtube.com/watch?v=LAyFL7lnVNA

In the video, I request a url which pushes a cacheable resource for "data".

If I fetch “data” using fetch() or XHR, it goes to the server rather than the HTTP/2 push cache.

If I fetch “data” using an image element, it gets it from the push cache & places it in the HTTP cache. Now, if I fetch with fetch()/XHR it comes from the HTTP cache.

Edge should allow XHR/fetch to use the push cache.

I only tested XHR/fetch/img, so there may be other APIs that don’t correctly use the push cache.


0 attachments

    Comments and activity

    • Edge also doesn’t use the push cache for iframes.

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

      Changed Assigned To to “Bogdan B.”

      Changed Assigned To from “Bogdan B.” to “AA”

    You need to sign in to your Microsoft account to add a comment.

    Sign in