Issue 2133393002: Serialize NPN_HTTP_2 as "h2" instead of "npn-h2".

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 2133393002: Serialize NPN_HTTP_2 as "h2" instead of "npn-h2". (Closed)

Created:
4 years, 5 months ago by Bence

Modified:
4 years, 5 months ago

Reviewers:
Ryan Hamilton

CC:
chromium-reviews, cbentzel+watch_chromium.org

Base URL:
https://chromium.googlesource.com/chromium/src.git@2785

Target Ref:
refs/pending/branch-heads/2785

Project:
chromium

Visibility:
Public.

Serialize NPN_HTTP_2 as "h2" instead of "npn-h2". This will allow properly parsing spec-compliant Alt-Svc headers. At the same time, still parse "npn-h2" so that old persisted settings can be read from disk. TBR=rch@chromium.org BUG=626375 Review-Url: https://codereview.chromium.org/2129973002 Cr-Commit-Position: refs/heads/master@{#404264} (cherry picked from commit 08352775a31f45a7ad5f280ee1a7b98315338844) Committed: https://chromium.googlesource.com/chromium/src/+/d4eaa8b08fcfea8e277aaee04e8c3a9d84d5f889

Created: 4 years, 5 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+20 lines, -30 lines)			Patch
	M	net/http/http_server_properties.cc	View		3 chunks	+16 lines, -26 lines	0 comments	Download
	M	net/http/http_server_properties_manager_unittest.cc	View		3 chunks	+4 lines, -4 lines	0 comments	Download

Total messages: 2 (1 generated)

Bence

4 years, 5 months ago (2016-07-09 14:41:42 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
d4eaa8b08fcfea8e277aaee04e8c3a9d84d5f889 (presubmit successful).