ERR_SPDY_PROTOCOL_ERROR
Reported by
shank.ia...@gmail.com,
Apr 18 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36 Example URL: https://2fa-devtest.cloud.oneidentity.com/dashboards/100528#/Settings Steps to reproduce the problem: 1.Create a trial account 2. Login to the url 3. click the settings tab you will see ERR_SPDY_PROTOCOL ERROR What is the expected behavior? it should show the page without any errors. affected call Request URL: https://2fa-devtest.cloud.oneidentity.com/Account/Token?requestId=0.8916489710216235 What went wrong? i saw all the request are passed successfully in chrome if it uses http 1.1 by disable the chrome using chrome.exe --disable-http2 with out this flag it is showing the error Does it occur on multiple sites: No Is it a problem with a plugin? No Did this work before? Yes 65 Does this work in other browsers? Yes Chrome version: 66.0.3359.117 Channel: stable OS Version: 10.0 Flash Version: +HTTP_TRANSACTION_READ_HEADERS [dt=214] t=23937 [st=216] HTTP2_STREAM_ERROR --> description = "Server reset stream." --> net_error = "ERR_SPDY_PROTOCOL_ERROR" --> stream_id = 49 t=23937 [st=216] -HTTP_TRANSACTION_READ_HEADERS --> net_error = -337 (ERR_SPDY_PROTOCOL_ERROR) t=23937 [st=216] -URL_REQUEST_START_JOB --> net_error = -337 (ERR_SPDY_PROTOCOL_ERROR) t=23937 [st=216] URL_REQUEST_DELEGATE [dt=0] t=23938 [st=217] -REQUEST_ALIVE --> net_error = -337 (ERR_SPDY_PROTOCOL_ERROR)
,
Apr 18 2018
Could you please attach the entire NetLog? Thanks!
,
Apr 19 2018
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
,
Apr 19 2018
Chrome sends a HEADERS frame to the server, 215 ms later it receives a RST_STREAM frame with error code PROTOCOL_ERROR. The request looks fine to me, and the HTTP/2 specification does not allow a RST_STREAM frame to have any more information for debugging, so I do not know why the server resets the stream. You might want to contact the server administrator and point them to this bug, they can look at server logs to see if they can dig up anything.
t=14482 [st=13019] HTTP2_SESSION_SEND_HEADERS
--> exclusive = true
--> fin = true
--> has_priority = true
--> :method: GET
:authority: 2fa-devtest.cloud.oneidentity.com
:scheme: https
:path: /Account/Token?requestId=0.5428871857277993
x-ms-request-id: 3T0r
authorization:
x-dell-auth-key: null
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36
cui: true
x-ms-request-root-id: +CDrI
accept: */*
referer: https://2fa-devtest.cloud.oneidentity.com/dashboards/100528
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9
cookie: [4424 bytes were stripped]
--> parent_stream_id = 0
--> source_dependency = 1994 (HTTP_STREAM_JOB)
--> stream_id = 131
--> weight = 220
t=14697 [st=13234] HTTP2_SESSION_RECV_RST_STREAM
--> error_code = "1 (PROTOCOL_ERROR)"
--> stream_id = 131
,
Apr 19 2018
,
Apr 19 2018
,
Apr 20 2018
Thanks
,
May 17 2018
Looks like this is working as intended, so I'm closing this bug. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by vamshi.kommuri@chromium.org
, Apr 18 2018