HTTP Application Cache - fallback is incorrectly invoked on redirect

Fixed Issue #8572187


Stefan F.
Aug 22, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Fixed in build #
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

Steps to reproduce

  • Have a website that includes a cache manifest with a FALLBACK section.
  • Let a GET request whose URL matches a fallback entry return a redirect (302) with a “Location:” header that only includes an absolute path.

Expected Result

The browser follows the redirect. This works with Edge 25.10586, IE 11, Firefox 48 and Chrome 52)

Actual result

Edge 38.14393 renders the fallback referenced in the cache manifest.


See for the relevant specification.
Attached you’ll find a simple ASP.NET MVC solution that can be used to reproduce the behavior.


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

    Changed Assigned To to “Venkat K.”

  • Are there any news on this? Since last week we have the first customers that cannot use our application because of this issue.

    I suspect their number will grow as Windows 10 Version 1607 is rolled out to the rest of the user base in the coming month…

  • Microsoft Edge Team

    Changed Assigned To from “Venkat K.” to “Rajat J.”

    Changed Status to “Confirmed”

    Changed Assigned To from “Rajat J.” to “Mohamed K.”

    Changed Assigned To from “Mohamed K.” to “Rajat J.”

    Changed Status from “Confirmed” to “In code review”

    Changed Status from “In code review” to “In progress”

    Changed Status from “In progress” to “Fixed”

  • Hello,

    Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 15063 and is available in our latest Insider Preview build.

    Best Wishes,
    The MS Edge Team

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

Sign in