Timeouts command returns an invalid status code of 43 instead of 13

Fixed, not yet flighted Issue #6762214

Details

Created
Mar 3, 2016
Privacy
This issue is public.
Reports
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

-> POST session/DA3BFB8F-D840-489E-A239-285EDC3C0600/timeouts

http://localhost:17556/session/DA3BFB8F-D840-489E-A239-285EDC3C0600/timeouts | {"type":"page load","ms":-1000}
{"Accept"=>"application/json", "Content-Type"=>"application/json; charset=utf-8", "Content-Length"=>"31"}
<- {"sessionId":"DA3BFB8F-D840-489E-A239-285EDC3C0600","status":43,"value":{"message":"Invalid argument"}}

Expected Results:

Status code of 13 not 43.

Actual Results:

Dev Channel specific:

Yes

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Kamen M.”

      Changed Assigned To to “Mara P.”

      Changed Assigned To from “Mara P.” to “Clay M.”

      Changed Status to “Confirmed”

      Changed Title from “Bad Error Status” to “Bad Error Status”

      Changed Assigned To from “Clay M.” to “Ben B.”

      Changed Title from “Bad Error Status” to “timeouts command returns an invalid status code of 43 instead of 13”

      Changed Assigned To from “Ben B.” to “Steven K.”

      Changed Assigned To from “Steven K.” to “Ben B.”

      Changed Assigned To from “Ben B.” to “Mustapha J.”

      Changed Status from “Confirmed” to “In progress”

      Changed Title from “timeouts command returns an invalid status code of 43 instead of 13” to “Timeouts command returns an invalid status code of 43 instead of 13”

      Changed Assigned To from “Mustapha J.” to “Stanley H.”

      Changed Assigned To from “Stanley H.” to “Clay M.”

      Changed Status from “In progress” to “Fixed”

    • This should be fixed in a future insiders build.

    • Microsoft Edge Team

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

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

    Sign in