New issue
Advanced search Search tips

Issue 921949 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

ERR_SPDY_PROTOCOL_ERROR randomly on XHR request

Reported by yannis.p...@gmail.com, Jan 15

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. 
2. 
3. 

What is the expected behavior?

What went wrong?
When we get it we refresh the browser a few times and the error goes away. We can't really reproduce the error but we have managed to capture a detailed chrome net log as it happens. There details of the request where it fails is below.

I would love someone's feedback or help on this as it doesnt happen on any other browser and we have ruled out server side issues.

89365: URL_REQUEST
https://api-domain.com/some/path?page=1&pageSize=10
Start Time: 2019-01-15 11:11:15.029
t=255420 [st=    0] +REQUEST_ALIVE  [dt=10068]
                     --> priority = "MEDIUM"
                     --> url = "https://api-domain.com/some/path?page=1&pageSize=10"
t=255421 [st=    1]    NETWORK_DELEGATE_BEFORE_URL_REQUEST  [dt=0]
t=255421 [st=    1]   +URL_REQUEST_START_JOB  [dt=10066]
                       --> load_flags = 17216 (DO_NOT_SAVE_COOKIES | DO_NOT_SEND_AUTH_DATA | DO_NOT_SEND_COOKIES | MAYBE_USER_GESTURE)
                       --> method = "GET"
                       --> url = "https://api-domain.com/some/path?page=1&pageSize=10"
t=255421 [st=    1]      NETWORK_DELEGATE_BEFORE_START_TRANSACTION  [dt=0]
t=255421 [st=    1]      HTTP_CACHE_GET_BACKEND  [dt=0]
t=255421 [st=    1]      HTTP_CACHE_OPEN_ENTRY  [dt=0]
t=255421 [st=    1]      HTTP_CACHE_ADD_TO_ENTRY  [dt=0]
t=255421 [st=    1]      HTTP_CACHE_READ_INFO  [dt=0]
t=255421 [st=    1]     +HTTP_STREAM_REQUEST  [dt=0]
t=255421 [st=    1]        HTTP_STREAM_JOB_CONTROLLER_BOUND
                           --> source_dependency = 89366 (HTTP_STREAM_JOB_CONTROLLER)
t=255421 [st=    1]        HTTP_STREAM_REQUEST_BOUND_TO_JOB
                           --> source_dependency = 89367 (HTTP_STREAM_JOB)
t=255421 [st=    1]     -HTTP_STREAM_REQUEST
t=255421 [st=    1]     +HTTP_TRANSACTION_SEND_REQUEST  [dt=1]
t=255421 [st=    1]        HTTP_TRANSACTION_HTTP2_SEND_REQUEST_HEADERS
                           --> :authority: api-domain.com
                               :method: GET
                               :path: /some/path?page=1&pageSize=10
                               :scheme: https
                               accept: application/json, text/plain, */*
                               accept-encoding: gzip, deflate, br
                               accept-language: en-US,en;q=0.9,el;q=0.8
                               origin: https://some-other-path.com
                               referer: https://some-other-path.com/
                               user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
                               x-somekey: random-guid
t=255422 [st=    2]     -HTTP_TRANSACTION_SEND_REQUEST
t=255422 [st=    2]     +HTTP_TRANSACTION_READ_HEADERS  [dt=10065]
t=265487 [st=10067]        HTTP2_STREAM_ERROR
                           --> description = "Server reset stream."
                           --> net_error = "ERR_SPDY_PROTOCOL_ERROR"
                           --> stream_id = 3
t=265487 [st=10067]     -HTTP_TRANSACTION_READ_HEADERS
                         --> net_error = -337 (ERR_SPDY_PROTOCOL_ERROR)
t=265487 [st=10067]   -URL_REQUEST_START_JOB
                       --> net_error = -337 (ERR_SPDY_PROTOCOL_ERROR)
t=265488 [st=10068]    URL_REQUEST_DELEGATE_RESPONSE_STARTED  [dt=0]
t=265488 [st=10068] -REQUEST_ALIVE
                     --> net_error = -337 (ERR_SPDY_PROTOCOL_ERROR)

Did this work before? Yes 

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 10.0
Flash Version:
 
Labels: Needs-Bisect Needs-Triage-M71
Components: -Internals>Network Internals>Network>HTTP2
This looks like an issue with the server resetting the stream for unclear reasons.  I don't think we can make forward progress here without information on that server.  It may be a bug with the server, since it's clearly not sending us what we asked it to.
Labels: Needs-Feedback
The server is just an HA Proxy. I cant see how this could be the problem as this hasnt changed for a very long time.
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 15

Cc: mmenke@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by swarnasree.mukkala@chromium.org, Jan 16 (6 days ago)

Cc: swarnasree.mukkala@chromium.org
Labels: -Needs-Bisect Triaged-ET TE-NeedsTriageHelp
The issue seems to be related to the server which is out of scope to triage from our end, hence adding TE-NeedsTriageHelp. As it is network specific issue removing Needs-Bisect and requesting someone from Internals>Network>HTTP2 to look into the issue and help in further triaging.

Thanks.!

Comment 7 by b...@chromium.org, Today (16 hours ago)

Labels: Needs-Feedback
Owner: b...@chromium.org
Please attach the log that you captured so that I can examine it.

Sign in to add a comment