Fetching unauthorized resource causes TypeMismatchError

Fixed, not yet flighted Issue #8653298

Details

Author
Ted d.
Created
Aug 26, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 6 people

Sign in to watch or report this issue.

Steps to reproduce

https://jsfiddle.net/r65zb0d8/

fetch('https://httpbin.org/status/401').then(resp => console.log('then', resp)).catch(e => console.log('catch', e)))
Execute this on httpbin.org and it will give a 401, which results in a TypeMismatchError.

Executing in chrome and FF results in the then being called with a usable object. I expect edge to behave in the same way, but right now it triggers the catch with the TypeMismatchError.

Please see other feedbacks in userfeedback VSO for feedbacks that are tracked by this work item.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Brandon M.”

      Changed Status to “Confirmed”

      Changed Steps to Reproduce

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

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

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

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

      Changed Status from “In progress” to “Fixed, not yet flighted”

    • We have fixed this and the fix has been checked in. You should see it show up in future releases.

      All the best,
      The MS Edge Team

    • Awesome, thanks!

      Any idea when consumers will see this release?

    • Microsoft Edge Team

      Changed Status from “Fixed, not yet flighted” to “Fixed, flighted”

      Changed Status from “Fixed, flighted” to “Fixed, not yet flighted”

      Changed Steps to Reproduce

    • I am still seeing this issue in Edge 14.14393?

    • @Esben A. Same here, it seems that the issue is not resolved yet or not released.

      @Brad E. Any idea when this fix is released in stable Edge?

    • I confirm that this issue can still be reproduced.
      I’m using Microsoft Edge 38.14393.0.0 (Microsoft EdgeHTML 14.14393) on Windows 10 Pro (64 bit, Version 1607).

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

    Sign in