Issue metadata
Sign in to add a comment
|
Too many redirects on Chrome 71
Reported by
misterda...@gmail.com,
Dec 27
|
||||||||||||||||||||
Issue descriptionExample URL: Steps to reproduce the problem: 1. 2. 3. What is the expected behavior? The page on the webview should be loaded successfully. What went wrong? When I use an android apps with Chrome 71 webview, there is a "Too many Redirects" page. When I downgrade to Chrome 70 and below, or change my webview implementation to Chrome Beta ver 72, the page loads fine. Did this work before? Yes Chrome ver 70 and Chrome Beta 72 Chrome version: 71.0.3578.99 Channel: stable OS Version: 8.0 Flash Version:
,
Dec 28
Thanks for the report. > or change my webview implementation to Chrome Beta ver 72, the page loads fine. Glad to hear it's fixed in M72. Bumping the priority down since it seems like the issue may already be resolved. I couldn't find any obvious crbug issues pointing to this problem. Could you list example apps this reproduces with? Could you also provide all the info from this bug template: https://goo.gl/9qkbdn
,
Dec 28
,
Jan 10
Not all Chrome 71 users are facing this issue. Only some are facing the issue. Example 1: I am on Singapore Telecom 4G network and on Chrome 71 webview, I perform flight search on the apps, the too many redirects happened. When I changed my connection to WIFI, it works fine. I downgraded to Chrome 66 Webview and on the same Singtel 4G network, it works fine. On WFI, it also works fine. I upgraded to Chrome 72 beta Webview. All works fine too. Example 2: Our vendors are in Moldova, they are using Chrome 71. Everything including 4G and WIFI works fine for them.
,
Jan 10
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
,
Jan 10
As Nate requested, could you please provide all the information requested in the template? At present we have no idea which application is affected, and under which circumstances.
,
Jan 10
If you want us to investigate this so you can find a workaround for users on 71, then you should try to produce a minimal test case that reproduces the bug and attach that - it's often very difficult for us to track down issues using real applications since we don't have the app's source code, and in this case it may be especially difficult since it might also depend on the behaviour of the webserver. We only have a limited amount of resources we can reasonably spend looking at issues that are already resolved on the latest version, so you need to provide as much information as you can. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by eroman@chromium.org
, Dec 27