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

Issue 689370 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

400 Bad Request on redirects if data saver enabled

Reported by stefan.s...@googlemail.com, Feb 7 2017

Issue description

Steps to reproduce the problem:
1. enable data saver
2. call http://www.noz.de/lokales/osnabrueck/artikel/846402/stadtwerke-feier-im-landgericht-osnack-hat-folgen
3. receive 400 Bad Request
4. disable data saver
5. call http://www.noz.de/lokales/osnabrueck/artikel/846402/stadtwerke-feier-im-landgericht-osnack-hat-folgen
6. page redirects to http://www.noz.de/lokales/osnabrueck/artikel/846402/stadtwerke-feier-im-landgericht-osnabrueck-hat-folgen with no error

What is the expected behavior?
You should be redirected instead of receiving an error page.

What went wrong?
Once you reach a redirect (and only on redirects) the site returns a 400 Bad Request only if data saver is enabled. If data saver is disabled the problem disappears. 
The remote address looks like a google server, so we don't know what we could do to fix this error.

Did this work before? N/A 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 6.0.1

It happens on various devices, versions and even on the desktop once the data saver is activated. We tried to work around this problem by using "Cache-Control: no-transform" but it doesn't help.

 
Cc: prashanthpola@chromium.org
Labels: triage-te
Components: -Platform>DevTools Internals>Network>DataProxy
Thanks for the report!
Forwarded it to related component.
Cc: -prashanthpola@chromium.org bengr@chromium.org
Labels: -triage-te M-56
Owner: megjab...@chromium.org
Status: Available (was: Unconfirmed)
We are able to repro the issue on Chrome Stable:56.0.2924.87 Device:Samsung Galaxy S6 /MMB29K/6.0.1 and HTC DESIRE 626S/MMB29M/6.0.1

@logcat http://go/chrome-androidlogs1/6/689370
Status: Assigned (was: Available)
Cc: -bengr@chromium.org
Owner: bengr@chromium.org

Comment 6 by bengr@chromium.org, Mar 17 2017

Owner: buettner@chromium.org
This is likely an issue with the compression proxy. Assigning to buettner@ to investigate. Note, I was able to reproduce.
Status: Fixed (was: Assigned)

Sign in to add a comment