Blimp: add support for SSL connections.

blimp/client/app/blimp_client_switches.h

Index: blimp/client/app/blimp_client_switches.h
diff --git a/blimp/client/app/blimp_client_switches.h b/blimp/client/app/blimp_client_switches.h
index 19b91ddd03d18cc36ec05c2987aa935e8b2f4991..0ae7e19c720f89cfd94f3ef6a0a30c9708407ae1 100644
--- a/blimp/client/app/blimp_client_switches.h
+++ b/blimp/client/app/blimp_client_switches.h
@@ -10,7 +10,18 @@
 namespace blimp {
 namespace switches {
 
-extern const char kBlimpletEndpoint[];
+// The path to the Engine's PEM-encoded X509 certificate.
+// If specified, SSL connected Engines must supply this certificate
+// for the connection to be valid.
+// e.g.:
+// --engine-cert-path=/home/blimp/certs/cert.pem
+extern const char kEngineCertPath[];
+
+// Specifies the blimplet scheme, IP-address and port to connect to, e.g.:
+// --engine-endpoint="tcp:127.0.0.1:25467".  Valid schemes are "ssl",

[Ryan Sleevi, 2016/02/23 21:01:31]

DOCUMENTATION: So it looks like you're intending to use this URL style, but
you've constructed a URL in the form we explicitly discourage (because it fails
to abide by the generic syntax)

Perhaps you meant tcp://127.0.0.1:25467, which would make more sense (the :// is
a special indicator of the relative syntax). This would also clarify what I
originally was going to ask, which is how to handle tcp://[::1]:25467 (that is,
are IPv6 literals in URL form or not)

[Kevin M, 2016/02/24 00:31:42]

Done.

+// "tcp", and "quic".
+// TODO(nyquist): Add support for DNS-lookup. See http://crbug.com/576857.
+extern const char kEngineEndpoint[];
 
 }  // namespace switches
 }  // namespace blimp