Open
Bug 1423536
Opened 8 years ago
Updated 3 years ago
h2 session errors bubble up as NS_ERROR_FAILURE, showing a blank page and not a proper error page
Categories
(Core :: Networking: HTTP, defect, P3)
Core
Networking: HTTP
Tracking
()
NEW
People
(Reporter: mayhemer, Unassigned)
Details
(Whiteboard: [necko-triaged])
Yesterday I had a case when an h2 session stopped responding. The log didn't have socket enabled, so I don't know what was that exactly, but looks like the server simply went down.
The problem I want to report is that the error on the connection and the h2 session 804b0014 (reset) was silently converted to 80004004 (FAILURE) so that when the load stopped I only seen a blank page, no explanation of what has happened.
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: V/nsHttp nsHttpConnection::OnSocketReadable [this=1EA5E400]
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: V/nsHttp max hang time exceeded!
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: V/nsHttp nsHttpConnectionMgr::ProcessPendingQ [ci=.S.....[tlsflags0x00000000]www.google.cz:443]
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: I/nsHttp Http2Session::WriteSegments 26812400 InternalState 1
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: I/nsHttp Http2Session 26812400 buffering frame header read failure 804b0014
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: V/nsHttp nsHttpConnection::OnSocketReadable 1EA5E400 trans->ws rv=804b0014 n=0 socketin=804b0014
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: V/nsHttp nsHttpConnection::CloseTransaction[this=1EA5E400 trans=26812400 reason=804b0014]
Http2Session @26812400
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: V/nsHttp nsHttpConnection::DontReuse 1EA5E400 spdysession=26812400
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: I/nsHttp Http2Session::DontReuse 26812400
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: I/nsHttp Http2Session::Close 26812400 804B0014
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: I/nsHttp MaybeDecrementConcurrent 26812400 id=0xD3 concurrent=4 active=1
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: I/nsHttp MaybeDecrementConcurrent 26812400 id=0xD1 concurrent=3 active=1
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: I/nsHttp Http2Session::CloseStream 26812400 209FB680 0xcf 80004004
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: I/nsHttp MaybeDecrementConcurrent 26812400 id=0xCF concurrent=2 active=1
2017-12-05 23:13:18.983000 UTC - [Socket Thread]: V/nsHttp nsHttpTransaction::Close [this=11721400 reason=80004004]
| Reporter | ||
Updated•8 years ago
|
Version: 54 Branch → Trunk
Updated•8 years ago
|
Priority: -- → P3
Whiteboard: [necko-triaged]
| Reporter | ||
Updated•8 years ago
|
Summary: h2 session errors bubbles up as NS_ERROR_FAILURE, showing a blank page and not a proper error page → h2 session errors bubble up as NS_ERROR_FAILURE, showing a blank page and not a proper error page
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•