400 Bad Request on redirects if data saver enabled
Reported by
stefan.s...@googlemail.com,
Feb 7 2017
|
|||||||
Issue descriptionSteps 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.
,
Feb 7 2017
Thanks for the report! Forwarded it to related component.
,
Feb 7 2017
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
,
Feb 10 2017
,
Feb 10 2017
,
Mar 17 2017
This is likely an issue with the compression proxy. Assigning to buettner@ to investigate. Note, I was able to reproduce.
,
Mar 30 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by rsgav...@chromium.org
, Feb 7 2017Labels: triage-te