New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 830501 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

|, {, } are not encoded as should be in RFC 7230 and RFC 3986

Reported by piotr.su...@respublica.org.pl, Apr 9 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Example URL:
http://localhost:8090/jira/browse/SSP-15?jql={|}

Steps to reproduce the problem:
1. Enter that url
2. Cry when Tomcat throws you with fatal stacktrace and you get 400

You need to use at least 8.5.12 tomcat or 9.0.0 to have this problem, because they comply to RFCs.

What is the expected behavior?
{|} characters are escaped

What went wrong?
{|} characters were not escaped

Did this work before? No 

Chrome version: 65.0.3325.181  Channel: stable
OS Version: OS X 10.13.4
Flash Version:
 
Cc: mkwst@chromium.org
[+mkwst], the owner of GURL (And also GURL::PathForRequest(), though I suppose if we escape these characters, we should probably do it while creating the URL, rather than when calling PathForRequest).

I agree with your reading of the spec, though no idea if we can safely change Chrome's behavior without a lot of fallout.
Labels: Needs-Triage-M65
Labels: Triaged-ET TE-NeedsTriageHelp
The issue seems to be out of TE-scope as it is related to running tomcat server. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!

Comment 4 by mmenke@chromium.org, Apr 11 2018

Status: Available (was: Unconfirmed)

Comment 5 by mmenke@chromium.org, Apr 18 2018

Cc: mmenke@chromium.org
Labels: Network-Triaged

Sign in to add a comment