Google Chrome 47.0.2526.73M broken NTLM proxy authentication

Seth Mos seth.mos at
Mon Dec 7 07:58:51 UTC 2015

A quick update, Google Chrome engineering did cut a new release with a
fix for this but it's not available yet.

The current workaround is to shrink your return headers smaller then
4096 bytes to prevent the authentication popup.

Get ready for a rough monday morning, we've already had to field quite a
few calls, and the GPO policy doesn't work, yay.

Dear Google, your internet browser doesn't browse the internet, please
make haste.

Kind regards,


Op 3-12-2015 om 9:04 schreef Seth Mos:
> Dear Google,
> As of Dec 2nd the Google Chrome 47.0.2526.73M breaks NTLM proxy
> authentication. This is unfortunate as nobody can get off the company
> network now, which is secure I suppose, but not quite what I had in mind.
> So if anybody gets called that Google Chrome is throwing a
> username/password prompt for every website you try, listing the website
> as the authentication domain, instead of the proxy server, this is for you.
> If you are ahead of the curve, you can make a GPO to disable Chrome
> updates for the time being until this is fixed. If the browser already
> updated, well, sorry.
> Kind regards,
> Seth

More information about the NANOG mailing list