The good news is that Chrome 44 fixed numerous bugs. The bad news is it also introduced a bug that causes some sites to fail to render properly while others fail completely with a ERR_TOO_MANY_REDIRECTS error message.
Google's development team is well aware of the problem and is working on getting the fix into the Chrome stable channel for an immediate update.
This bug started from the best of intentions. The code was meant to encourage the use of HTTPS for a more secure Web experience. Unfortunately, instead of encouraging the use of a secure link, if one was available, it forced the web browser to redirect to HTTPS pages... even if there were none available, This happened regardless of the web-server's htaccess settings or plugin directives even on sites that have never used https.
For the most part, this problem is being seen in self-hosted Wordpress sites. It's not limited to those. Other sites that don't support HTTPS or use a mix of HTTP and HTTPS pages are also being affected.
As one bug reporter put it, "This bug [is] critical, you need to push a fix ASAP. 'Soonish' is not going to cut it."
He continued, " The Internet is starting to react to this bug. Users are starting to adopt 3rd party plugins and patches to fix the issue from their end, this could lead to even more trouble down the road. It should never have made it into a stable release in the first place, as it is obvious the amount of breakage it causes."
Google's development team is well aware of the problem and is working on getting the fix into the Chrome stable channel for an immediate update.
This bug started from the best of intentions. The code was meant to encourage the use of HTTPS for a more secure Web experience. Unfortunately, instead of encouraging the use of a secure link, if one was available, it forced the web browser to redirect to HTTPS pages... even if there were none available, This happened regardless of the web-server's htaccess settings or plugin directives even on sites that have never used https.
For the most part, this problem is being seen in self-hosted Wordpress sites. It's not limited to those. Other sites that don't support HTTPS or use a mix of HTTP and HTTPS pages are also being affected.
As one bug reporter put it, "This bug [is] critical, you need to push a fix ASAP. 'Soonish' is not going to cut it."
He continued, " The Internet is starting to react to this bug. Users are starting to adopt 3rd party plugins and patches to fix the issue from their end, this could lead to even more trouble down the road. It should never have made it into a stable release in the first place, as it is obvious the amount of breakage it causes."
