Edge Response-Status never recieved when Server returns 503 Statuscode

Fixed, not yet flighted Issue #11201876

Details

Created
Mar 8, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
38.14393
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

We tried to load this URL:
https://unavailable.test.meisterplan.io/

which is a Test-Endpoint to display our Maintenance-Site. It returns a 503 HTTP Status Code. When loading this URL with Edge, the first request seems (accoring to the Network Tab) never ending, so a Response Header is never available in the Network Tab (see the attached Screenshot).

If the URL is requested a second time the 503 is shown in the network tab. This can be repeated, so each first request seems to never get a response while each second request recieves one.

Another strange thing is, that the Response Header seems to be written to the html-body (according to the dom-explorer-tab, Screenshot also available). Also the box in the middle of the page always jumps around in each second request.

Thank you for taking a look at the issue!
Best Regards
Matthias

Version Info:
Microsoft Edge 38.14393.0.0
Microsoft EdgeHTML 14.14393

Attachments

Comments and activity

  • Microsoft Edge Team

    Changed Status to “Confirmed”

    Changed Assigned To to “Mike J.”

    Changed Assigned To from “Mike J.” to “Jordan B.”

    Changed Status from “Confirmed” to “In progress”

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

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

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

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

Sign in