content length set to 0 issue causing fetch put/patch requests to fail

Fixed, not yet flighted Issue #7773267

Details

Created
Jun 2, 2016
Privacy
This issue is public.
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Attachments

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Ali A.”

  • Filing this on behalf of @davidgraham: https://twitter.com/davidgraham/status/738473923386302464

  • Microsoft Edge Team

    Changed Title from “0 issue causing fetch put/patch requests to fail” to “content length set to 0 issue causing fetch put/patch requests to fail”

    Changed Assigned To from “Ali A.” to “Rob T.”

    Changed Assigned To from “Rob T.” to “Brandon M.”

    Changed Status to “Confirmed”

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

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

    Changed Assigned To from “Brandon M.” to “Greg W.”

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

  • Hello,

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

    Best Wishes,
    The MS Edge Team

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

Sign in