Issue 305213002: Do not mark QUIC as *broken* when a 0-RTT fails because this prevents us

Issue 305213002: Do not mark QUIC as broken when a 0-RTT fails because this prevents us (Closed)

Created:
6 years, 6 months ago by Ryan Hamilton

Modified:
6 years, 6 months ago

Reviewers:
ramant (doing other things)

CC:
chromium-reviews, cbentzel+watch_chromium.org

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Visibility:
Public.

More Reviews

Description

Do not mark QUIC as *broken* when a 0-RTT fails because this prevents us from verifying that TCP is also working. So instead, mark it as "recently broken" which requires handshake confirmation. Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=274010

Patch Set 1 #

Created: 6 years, 6 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+37 lines, -15 lines)			Patch
M	net/http/http_server_properties_impl.cc	View	1 chunk	+4 lines, -5 lines	0 comments	Download
M	net/quic/quic_network_transaction_unittest.cc	View	1 chunk	+5 lines, -0 lines	0 comments	Download
M	net/quic/quic_stream_factory.cc	View	1 chunk	+28 lines, -10 lines	0 comments	Download

Messages

Total messages: 9 (0 generated)

Expand Messages | Collapse Messages

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/rch@chromium.org/305213002/1

6 years, 6 months ago (2014-05-30 21:22:30 UTC) #4

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/rch@chromium.org/305213002/1

6 years, 6 months ago (2014-05-30 22:45:02 UTC) #8

Message was sent while issue was closed.

Change committed as 274010

Expand Messages | Collapse Messages