Microsoft Edge handles <object> Oddly

Issue #8499759 • Assigned to Sermet I.


Jonathan S.
Aug 16, 2016
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Found in build #
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

Ignore the bottom, original report. The user was returning a 204 response, which understandably prevented a follow-up GET.

That being said, Edge still makes two trips, for each object[data], unlike Chrome and Firefox. Edge does a HEAD, then GET. Chrome and Firefox do a simple GET.

When Microsoft Edge encounters <object data='/foo'></object>, it fires off an initial HEAD request to gather meta-data about the source. Following this, a GET request is made for the content of the source.

Because the initial request is a HEAD request, and thus explicitly forbids body content, it seems reasonable to respond to this request with a 204 No Content message. Oddly, Microsoft Edge treats the 204 as reason to terminate the process entirely, thus making no follow-up GET request for content.

Repro Steps:

  1. Download Object Data
  2. npm install
  3. node index.js
  4. Navigate to http://localhost:3000/
  5. Observe network traffic

Internet Explorer, and Microsoft Edge take the two-step approach.
Google Chrome, Mozilla Firefox, Opera, and Brave make a single GET request.

Originally reported on Stack Overflow.


Comments and activity

  • Microsoft Edge Team

    Changed Steps to Reproduce

    Changed Assigned To to “Brad E.”

    Changed Assigned To to “Venkat K.”

    Changed Assigned To from “Venkat K.” to “Mohamed K.”

    Changed Assigned To to “Sermet I.”

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

Sign in