Issue metadata
Sign in to add a comment
|
Chrome rendering broken after NTLM authentication
Reported by
mark.ode...@gmail.com,
May 2 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Steps to reproduce the problem: See detailed description in the attachment. What is the expected behavior? What went wrong? Rendering of the application fails. Did this work before? Yes 65 Chrome version: 66.0.3359.139 Channel: stable OS Version: 10.0 Flash Version:
,
May 3 2018
Thanks for filing the issue! @Reporter: As per comment#1 steps to reproduce the problem, after going through the attached file, to test the issue from our end we need the sample URL and valid login credentials to confirm the issue, if possible could you please provide the sample URL and valid login credentials which helps us in further triaging it. Thanks!
,
May 3 2018
,
May 9 2018
Hi All Unfortunately, this is not so easy. It is an internal application which is not accessible from the internet. So I can't provide you with the URL and valid credentials. Do you have a process in place for such an application? If not, we could offer an online screen sharing session in order to support pinpointing the problem. Would that help? Thank you for your answer and kind regards Mark Odermatt 2018-05-03 8:52 GMT+02:00 viswa.ka… via monorail < monorail+v2.1886622140@chromium.org>:
,
May 9 2018
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
,
May 9 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, May 2 2018