Issue metadata
Sign in to add a comment
|
Using a proxy with basic authentication will load Dom but render the page blank
Reported by
glen...@gmail.com,
May 9 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Connect to a site that requires a proxy with basic authentication 2. Enter credentials and save them and page will load just fine 3. Close browser and reopen. 4. Enter same URL in url bar and hit enter (Use saved credentials). Page will load but screen is blank and the URL bar will show no URL. If you check the DOM it is loaded and if you click into the URL bar and hit escape it will show the URL. Refreshing or hitting enter on the url bar will load the page correctly. I have noticed that sometimes it takes 2+ times of closing the browser but most of the time it will happen the first time. What is the expected behavior? The page should load every time you open it. What went wrong? From a networking standpoint everything looks correct. The page rendering just doesn't work on next load of a site with basic auth. See steps to reproduce. Did this work before? Yes 65 Chrome version: 66.0.3359.139 Channel: stable OS Version: OS X 10.13.3 Flash Version:
,
May 10 2018
,
May 10 2018
Team do not have proxy setup as of now to test this issue from our end. Hence adding appropriate component.Could someone from Internals>Network>Proxies team please have a look at this issue.
,
May 10 2018
Thank you for your report. Any chance you could provide a NetLog as described in https://www.chromium.org/for-testers/providing-network-details ?
,
May 10 2018
Maybe this is related to issue 840176 / issue 839724 ? Suspect this is more likely an auth issue rather than a proxy one.
,
May 10 2018
If I provide a netlog would it show any URL information> We are a health company accessing patient data and I don't want to cause a HIPPA violations.
,
May 10 2018
So I was beating my brains last night and whatever you guys did in 68.0.3426.0 seems to have fixed our issue.
,
May 10 2018
glenbot: Thanks for the update! We certainly wouldn't want to compromise patient privacy (Logs should only contain URLs, but yea, seems like a really bad idea, with anything confidential). Fortunately, it looks like 68.0.3426.0 includes the fix from issue 840176 , so this is almost certainly the same issue, and we don't need any more information from you. We'll be merging the fix to Chrome 67 (And I suspect Chrome 66 as well).
,
May 10 2018
Thank you!
,
May 10 2018
Thanks for the report! As an aside, I **STRONGLY** urge doing an audit of whatever legacy system is relying on a proxy using Basic auth. An HTTP proxy using Basic auth offers absolutely no security or privacy. Usernames and passwords are sent over the network in the clear! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by glen...@gmail.com
, May 9 2018