XmlHttpRequest readyState 4 not triggered for cached (304) response

Not reproducible Issue #101079


Apr 27, 2014
This issue is public.
Found in build #
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce

URL = http://postfix.futurete.ch/test2.html
Repro Steps:
A test page can be found at http://postfix.futurete.ch/test2.html

  1. Create an XHR
  2. Attach an onreadystatechange handler which, in response to readyState 1 triggers send().
  3. Open the XHR to a CORS enabled/cacheable resource
    Expected: readyState 4 triggers
    Actual: readyState 4 triggers first time only

Expected Results:

Calling xhr.send() from an onreadystatechange (when readyState 1) handler should be no different from calling it outside the handler.
An XHR sent to a previously cached resource should trigger readyState 4.

Actual Results:


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “IPBS P.”

      Changed Assigned To from “IPBS P.” to “Bruce M.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Sekhar B.”

      Changed Status to “Confirmed”

      Changed Steps to Reproduce

      Changed Assigned To from “Sekhar B.” to “David W.”

      Changed Assigned To from “David W.” to “IPBS P.”

      Changed Status from “Confirmed” to “Not reproducible”

      Changed Assigned To from “IPBS P.” to “Venkat K.”

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

    Sign in