Add TLS-SRP (RFC 5054) support

chrome/browser/autocomplete/autocomplete.cc

Index: chrome/browser/autocomplete/autocomplete.cc
diff --git a/chrome/browser/autocomplete/autocomplete.cc b/chrome/browser/autocomplete/autocomplete.cc
index bd8cf16f932b4e340438f80bbf8d505bb1f714fd..3785ca76aae44b51a08403930abb6f05aeddf750 100644
--- a/chrome/browser/autocomplete/autocomplete.cc
+++ b/chrome/browser/autocomplete/autocomplete.cc
@@ -149,15 +149,16 @@ AutocompleteInput::Type AutocompleteInput::Parse(
     return URL;
   }
 
-  // If the user typed a scheme, and it's HTTP or HTTPS, we know how to parse it
-  // well enough that we can fall through to the heuristics below.  If it's
-  // something else, we can just determine our action based on what we do with
-  // any input of this scheme.  In theory we could do better with some schemes
-  // (e.g. "ftp" or "view-source") but I'll wait to spend the effort on that
-  // until I run into some cases that really need it.
+  // If the user typed a scheme, and it's HTTP, HTTPS, or HTTPSV we know how to
+  // parse it well enough that we can fall through to the heuristics below.  If
+  // it's something else, we can just determine our action based on what we do
+  // with any input of this scheme.  In theory we could do better with some
+  // schemes (e.g. "ftp" or "view-source") but I'll wait to spend the effort on
+  // that until I run into some cases that really need it.
   if (parts->scheme.is_nonempty() &&
       !LowerCaseEqualsASCII(parsed_scheme, chrome::kHttpScheme) &&
-      !LowerCaseEqualsASCII(parsed_scheme, chrome::kHttpsScheme)) {
+      !LowerCaseEqualsASCII(parsed_scheme, chrome::kHttpsScheme) &&
+      !LowerCaseEqualsASCII(parsed_scheme, chrome::kHttpsvScheme)) {
     // See if we know how to handle the URL internally.
     if (net::URLRequest::IsHandledProtocol(UTF16ToASCII(parsed_scheme)))
       return URL;