New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 596692 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

XMLHttpRequest.statusText is blank instead of "OK"

Reported by alanwa...@gmail.com, Mar 21 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Steps to reproduce the problem:
1. Send an Ajax request using an XMLHttpRequest.
2. Wait for a readyState of 4
2. Examine the statusText.

What is the expected behavior?
The statusText should be "OK".

What went wrong?
The statusText is an empty string "".

Did this work before? Yes Last stable build of Chrome.

Chrome version: 49.0.2623.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

There are a few places in an old web application that are still using the AjaxPro framework for making ajax requests. That framework is checking for a status of 200 and a statusText of "OK" (why it's checking for both, I don't know) and is failing now that the statusText is blank.
 
Cc: yhirano@chromium.org
Components: Internals>Network>HTTP2
See  issue 475223 .
Cc: b...@chromium.org rnimmagadda@chromium.org
@bnc: Could you please let us know if this issue is related to "475223".

Thank you.

Comment 3 by alanwa...@gmail.com, Mar 22 2016

It does appear to be. The protocol is HTTP/2.

I assume I'll need to write a handler to send the statusText for these requests and/or move to a different Ajax solution (which we have been, this is a legacy service).

Thanks.

Comment 4 by b...@chromium.org, Mar 23 2016

Status: WontFix (was: Unconfirmed)
This is working as intended.  HTTP/2 does not specify a status text in the response.  The AjaxPro framework will need to be updated to account for this.

Sign in to add a comment