New issue
Advanced search Search tips

Issue 772381 link

Starred by 2 users
Status: WontFix
Owner:
b...@chromium.org
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

URL parsing error results in ERR_SPDY_PROTOCOL_ERROR

Reported by centbrwf...@gmail.com, Oct 6 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Example URL:

Steps to reproduce the problem:
Visit
https://click.rambler.ru/eyJhbGciOiAiUlMyNTYiLCAia2lkIjogImNybS1wcm9kLWtleS0xIn0.eyJ1cmwiOiAiaHR0cHM6Ly93d3cuZ2F6ZXRhLnJ1L2N1bHR1cmUvMjAxNy8xMC8wNS9hXzEwOTE4MzEwLnNodG1sP2RhdGVzdWJzY3JpYmU9MDUxMDIwMTcmXG51dG1fc291cmNlPWVtYWlsJmFtcDt1dG1fbWVkaXVtPWdhemV0YV9kYWlseSZhbXA7dXRtX2NhbXBhaWduPTIwMTctMTAtMDVcbiIsICJhY3Rpb24iOiAicnQiLCAiY3RpbWUiOiAxNTA3MjA5NzIwLjg3MTMxMSwgImV4dHJhIjogeyJtZXNzYWdlX2lkIjogIjI3OWExY2RjLTJmYjEtNGE1YS05NDAxLTJmNDk5OWYyMjM2Ni03YmZiY2Y5MS1lYWU3LTRiMzUtYjQ3Yy1kNWM4MGNjZDM1OTAtMTUwNzIwOTcyMCIsICJlbWFpbCI6ICJsa29uaWtvdkBnbWFpbC5jb20ifX0.ZoRUS1JFKEyHvURYMb340G95dvq4RfwGZ8qw0aWwuNYrUDl7ZZc2CmlCCr52GbNM7OTLOFxq5wmrNwH6wRiYpqIRvU8YlKz5nvxnbiwa23i42iGZHG0qDvPHA5ONXjkJ2LaddlSAPfOYbR6FXLOz_cwl6e4vrOPBTRDoC05zWD3k6v-cGIWZV0AdkpbrhSRRDd_I1DodaMxEeTUDwQ37ZXKNpAuMeUsMC7dCIy-XvVM_CD6AbfSrGQjQiUTwqZFXHnrkCFbBHrmpjfAkDOJ9LnCnRs9bM0VEKcckHmQLTuCbi_Cjjoi7rh1eflYZZBLBCrMk-TQWxhVmILfVOhRXPw

What is the expected behavior?
The web page should be opened normally as in Edge and Firefox.

What went wrong?
ERR_SPDY_PROTOCOL_ERROR seen.
HeaderCoalescer::OnHeader receives a key "utm_source=email&utm_medium=gazeta_daily&utm_campaign=2017-10-05", it contains HTML characters. Chromium treats it as an error response. This happened from Chrome 58.

Did this work before? Yes 57.0.2987.133

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 10.0 (Windows 10)
Flash Version: Shockwave Flash 27.0 r0

Comment 1 by mmenke@chromium.org, Oct 6 2017

Components: -Internals>Network Internals>Network>HTTP2
I don't think ampersands or semi-colons are allowed in header keys, so this may be working as intended.

Comment 2 by b...@chromium.org, Oct 6 2017

Owner: b...@chromium.org
Status: WontFix (was: Unconfirmed)
I can reproduce:
t=201675 [st=131]  HTTP2_SESSION_RECV_INVALID_HEADER
                   --> error = "Invalid character in header name."
                   --> header_name = "utm_source=email&utm_medium=gazeta_daily&utm_campaign=2017-10-05"
                   --> header_value = ""

RFC 7230 Section 3.2 defines header fields ("header-field"), the header key is "field-name", which is "token", defined in Section 3.2.6 to be "1*tchar", which cannot be semi-colon.  (Amperstand is allowed though.)  So the response header key is invalid.  This is working as intended.

Comment 3 by centbrwf...@gmail.com, Oct 6 2017 

thanks for the explanation.
►

Sign in to add a comment