SSL Authentication Failed
Reported by
shalon...@gmail.com,
Sep 13 2017
|
||||||
Issue descriptionSteps to reproduce the problem: UE cannot access the following URL by browser. URL1 : https://www.amazon.co.jp/?tag=hydraamazonav-22&hvadid=163750918017&hvpos=1t1&hvnetw=g&hvrand=974275034235801197&hvpone=&hvptwo=&hvqmt=e&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=1028853&hvtargid=kwd-893523692&ref=pd_sl_8eaqjij3p0_e URL2 : https://sbapi.tobila.com/files/rule.html URL3 : https://www.geotrust.co.jp/ URL4 : https://slabo.backlog.jp/LoginDisplay.action What is the expected behavior? What went wrong? UE cannot access the following URL by browser. These website are using SSL. URL1 : https://www.amazon.co.jp/?tag=hydraamazonav-22&hvadid=163750918017&hvpos=1t1&hvnetw=g&hvrand=974275034235801197&hvpone=&hvptwo=&hvqmt=e&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=1028853&hvtargid=kwd-893523692&ref=pd_sl_8eaqjij3p0_e URL2 : https://sbapi.tobila.com/files/rule.html URL3 : https://www.geotrust.co.jp/ URL4 : https://slabo.backlog.jp/LoginDisplay.action If user changed the time settings to past date, this issue does not occur. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 54.0.2840.2636560 Channel: n/a OS Version: 6.1 Flash Version: Shockwave Flash 22.0 r0
,
Sep 13 2017
Unable to reproduce the issue using #60.0.3112.116 on Android 6.0.1; SM-J710F Build/MMB29K as per the steps mentioned in comment #0. Able to access the above mentioned URL's. @shalong07: Could you please upgrade your Chrome to the latest version and check if you still face the issue? Thanks!!
,
Sep 14 2017
Hi friend, As we have done lots of implementations and changes based on current Chrome v54,and we have already moved into MP phase with all these well tested for many rounds. So we really not suggest to upgrade to another version at this period. Could you please provide the patch? thanks.
,
Sep 14 2017
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 5 2017
,
Oct 5 2017
Note we only provide support for the current versions of Chromium and Chrome, which is 61 or later. For earlier versions, it's self-supported debugging. Can you confirm that it works on the current Stable, as suggested in Comment #2? If you're building a custom distribution of Chromium (as implied in Comment #3), you'll need to debug yourselves, such as using a NetLog. It's possible you're running into an issue with Certificate Transparency, fixed in Chrome 56, or by using the content embedder API to specify settings appropriate for your application. However, as I mentioned, as that's such an old version, it's not possible to provide support for that.
,
Oct 11 2017
,
Oct 20 2017
Closing due to lack of feedback. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by shalon...@gmail.com
, Sep 13 2017