Actually, given that we won't get a stable channel push for just this, I think we need to break that redirect now (take it to a more generic HC article). Maybe have a "if you are the site administrator and see ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION, see xyz" message in the corner and link that one where it goes now.

Then we can separately merge changes to have more distinct URLs between them if we want.

Sorry, it seems like the SSL protocol addition to the HC article dropped off from the original request. 

In my HC request I asked for:

The server returned an invalid response 
If you see this error, it means the website returned a response Chrome could not understand. The website owner will need to resolve the problems for it to be accessible. 

For website administrators: 
If the error shows ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION, this means the server has a bug in its SSL implementation. In the past, Chrome may have worked around this, but doing so affected the security of all sites, so this has been removed. Ensure your server software is up-to-date. If the problem persists, contact your software vendor. 

Enterprise administrators who need more time to fix internal services may set the SSLVersionFallbackMin policy to tls1.1 to temporarily re-enable the workaround. For details, see [Set Chrome policies for devices]. This will be removed in September 2016, so servers should still be fixed. 

So we can request for: 

The server returned an invalid response 
If you see this error, it means the website returned a response Chrome could not understand. The website owner will need to resolve the problems for it to be accessible. 

If you are the site administrator and see ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION read the <developer article>.

to be added to: https://support.google.com/chrome/answer/6098869?p=dh_error&rd=1

HC updates request made at: b/28433726

I guess for the code update, I should create a separate TLS learn more link? 

If we're going with not having these links go to generic per-user-error HC articles, then it should be specific to the per-developer-error ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION error code, yeah. (Nitpick: Not sure what you mean by "TLS learn more" link. This is a particular error we can get when trying to establish a TLS connection, not something general about SSL/TLS.)

> (Nitpick: Not sure what you mean by "TLS learn more" link. This is a particular error we can get when trying to establish a TLS connection, not something general about SSL/TLS.

Yes, a learn more link about the ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION error. 

edwardjung: Ping. We really should take these links away for M52 and M51.

Apologies, got caught up with other work. I didn't realise we were taking them both away. I'll get a CL for review today.

I thought we ended up deciding that link didn't work out very well. The HC text was intended to be temporary, so we'd want this link to go away fairly quickly.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c0eef912c1bcb683a719a3376f307c7ae925adc1

commit c0eef912c1bcb683a719a3376f307c7ae925adc1
Author: edwardjung <edwardjung@chromium.org>
Date: Tue May 17 20:22:40 2016

Remove learn more links for SSL_PROTOCOL_ERROR and ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION

BUG= 607052 

Review-Url: https://codereview.chromium.org/1979213002
Cr-Commit-Position: refs/heads/master@{#394212}

[modify] https://crrev.com/c0eef912c1bcb683a719a3376f307c7ae925adc1/components/error_page/common/localized_error.cc