New issue
Advanced search Search tips

Issue 607012 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

statusText for some HTTP requests always empty, even though server sends it

Project Member Reported by va...@google.com, Apr 26 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Open new tab. 
2. Open Developer Tools > Network.
3. In this tab open some page that'd give you 404, e.g. https://bugs.chromium.org/asdf.
4. Click on the failed request in Developer Tools to see the response details.
5. Save the requests/responses as HAR by right-clicking in the requests list and choosing "Save as HAR with Content".

What is the expected behavior?
After step 4, "Status Code: 404 Not Found" is shown.

After step 5, HAR file statusText for the failed request has value "Not Found".

What went wrong?
After step 4, "Status Code: 404" is shown.

After step 5, HAR file statusText for the failed request has empty value.

Did this work before? Yes 

Chrome version: 50.0.2661.86  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 21.0 r0

This looks related to https://bugs.chromium.org/p/chromium/issues/detail?id=562599.

If the failed request happens during XHR, a message in JS console appears that says something like:

GET https://foo.com/bar 404 ()

Note the empty parenthesis.
 

Comment 1 by mmenke@chromium.org, Apr 27 2016

Status: WontFix (was: Unconfirmed)
If you request https://bugs.chromium.org/asdf, the server is not sending any status text, just a status code.  Note that HTTP/2 doesn't include any status text.

Here are the headers for the request (Note that the status line is bogus):

                         --> HTTP/1.1 404
                             status: 404
                             content-type: text/html; charset=UTF-8
                             content-encoding: gzip
                             x-google-appengine-module: default
                             x-google-appengine-version: 3884-93a9605
                             x-google-appengine-appid: s~monorail-prod
                             x-google-gfe-cloud-project-number: 679746765624
                             vary: Accept-Encoding
                             date: Wed, 27 Apr 2016 21:00:16 GMT
                             server: Google Frontend
                             cache-control: private
                             x-google-netmon-label: /bns/vr/borg/vr/bns/apphosting/prod-appengine.edge.frontend/5
                             content-length: 127
                             x-google-gfe-request-trace: vnbg64:9806,vsa6:6599,/bns/vr/borg/vr/bns/apphosting/prod-appengine.edge.frontend/5,vsa6:6599,vnbg64:9806
                             alt-svc: quic=":443"; ma=2592000; v="33,32,31,30,29,28,27,26,25"
                             x-google-gslb-service: apphosting
                             x-google-backends: /bns/jc/borg/jc/bns/apphosting/prod-appengine.appserver/637,jct66.prod.google.com:4463,/bns/vr/borg/vr/bns/apphosting/prod-appengine.edge.frontend/5,vsa6:6599,/bns/vs/borg/vs/bns/gfe-prod/shared-gfe_23_silos/42.gfe,vnbg64:9806
                             x-google-dos-service-trace: main:apphosting,dasher:apphosting
                             x-google-service: apphosting,apphosting
                             x-google-gfe-response-code-details-trace: response_code_set_by_backend,response_code_set_by_backend
                             x-google-gfe-response-body-transformations: chunked
                             x-google-gfe-service-trace: apphosting,dasher_zoo_responder,apphosting

Comment 2 by va...@google.com, Apr 27 2016

Confirmed: Making a request to HTTP/1.1 server with Data Saver extension turned off causes the status text to reappear. Filed #607328 to make the used protocol more clear.

Sign in to add a comment