New issue
Advanced search Search tips

Issue 888303 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 24
Cc:
phanindra.mandapaka@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

"Error 400 (Bad Request)!!1" on accessing certain sites

Reported by maxfield...@gmail.com, Sep 23 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Example URL:
https://www.google.com/chrome/

Steps to reproduce the problem:
1. Navigate to one of:
    a. https://www.google.com/chrome/
    b. https://www.google.com/alerts
    c. https://www.google.com/business/
    d. https://www.google.com/maps

What is the expected behavior?
Access and use the desired page without errors.

What went wrong?
HTTP 400 errors instead of either successfully visiting the site (for chrome, alerts, and business) or using Google Maps.

Of the listed URLs, only Maps loads the basic interface, but it is unable to load resources required to actually make use of Maps.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 69.0.3497.100  Channel: stable
OS Version: OS X 10.12.4
Flash Version: 

This used to occur on various Google sites intermittently with past versions of Chrome on macOS, but appeared to have been fixed for a time (can't be sure due to infrequent nature). Currently, this behavior is much more consistent than in the past.

Issue persists after disabling all extensions, as well as any running programs which could conceivably affect network traffic (nginx, zerotier, DNScrypt, etc.).

Note that "Error 400 (Bad Request)!!1" is not a typo or editorialization, but rather the tab title.
Screen Shot 2018-09-23 at 12.14.40 AM.png
304 KB View Download
Screen Shot 2018-09-23 at 12.20.08 AM.png
321 KB View Download
Screen Shot 2018-09-23 at 12.21.37 AM.png
305 KB View Download

Comment 1 by maxfield...@gmail.com, Sep 23 

Re-attaching example of 400 errors accessing Maps, original included possibly identifying information.
Screen Shot 2018-09-23 at 12.41.52 AM.png
1.1 MB View Download

Comment 2 by vamshi.kommuri@chromium.org, Sep 23

Labels: Needs-Triage-M69

Comment 3 by tkent@chromium.org, Sep 24

Components: -Blink Internals>Network

Comment 4 by phanindra.mandapaka@chromium.org, Sep 24

Cc: phanindra.mandapaka@chromium.org
Labels: Needs-Feedback Triaged-ET
maxfieldlehman@ Thanks for the issue...

Unable to reproduce the issue on reported chrome version 69.0.3497.100 using Mac 10.13.6.Attaching screen-cast for reference.
Steps: 
---------
1. Launched reported chrome 
2. Navigated the URL's on comment #0
As we are able to Access and use the desired page without errors.

@Reporter: Request you to retry this issue with fresh profile without any extensions & apps or reset all the flags and let us know if issue still persists.

Thanks.!
888303.mp4
2.4 MB View Download

Comment 5 by nhar...@chromium.org, Sep 24 

If you are able to reproduce this in a fresh profile, can you capture a net-log dump and attach it to the bug report? Instructions at https://www.chromium.org/for-testers/providing-network-details

Comment 6 by maxfield...@gmail.com, Sep 24 

I was not able to reproduce the issue on a fresh profile. Attempting to do so and comparing the requests themselves pointed me to the culprit, a large number of cookies created by an extension (relevant issue at https://github.com/deanoemcke/thegreatsuspender/issues/573).

If a 400 error is the expected behavior in this case, then this can be closed.
Project Member

Comment 7 by sheriffbot@chromium.org, Sep 24

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by nhar...@chromium.org, Sep 24

Status: WontFix (was: Unconfirmed)
Thanks for reporting back. This sounds like either an issue with The Great Suspender in how it manages cookies, or with google services behaving oddly with a certain subset of cookies presented. (The browser has limits on how many cookies it will store, both per-site and globally.)
►

Sign in to add a comment