An implementation of chrome.socket.secure().

chrome/browser/extensions/api/socket/socket.h

Index: chrome/browser/extensions/api/socket/socket.h
diff --git a/chrome/browser/extensions/api/socket/socket.h b/chrome/browser/extensions/api/socket/socket.h
index 2e73cb0d1fee27a496af8b9d77ca2f0a4391b8e5..422d0cd8842e9022e26bbd9e434ae233e5e3c9d0 100644
--- a/chrome/browser/extensions/api/socket/socket.h
+++ b/chrome/browser/extensions/api/socket/socket.h
@@ -45,6 +45,12 @@ class Socket : public ApiResource {
   };
 
   virtual ~Socket();
+  void SetOriginalHostname(const std::string& original_hostname) {
+    original_hostname_ = original_hostname;
+  }
+  const std::string& OriginalHostname() {
+    return original_hostname_;
+  }
   virtual void Connect(const std::string& address,
                        int port,
                        const CompletionCallback& callback) = 0;
@@ -102,7 +108,8 @@ class Socket : public ApiResource {
                         const net::CompletionCallback& callback) = 0;
   virtual void OnWriteComplete(int result);
 
-  const std::string address_;
+  // The name given to Connect(), used when verifying a TLS certificate.
+  std::string original_hostname_;

[Ryan Sleevi, 2013/11/25 17:30:13]

nit: naming wise, original_hostname_ seems a bit confusing, in that it's not
clear what a socket's "original" hostname means, and when/how an alternative
hostname might be returned.

Is there a reason this isn't just called Hostname? And does this need to be on
the base Socket interface, or should this be kept for the derived interface?

[Lally Singh, 2013/12/05 17:07:12]

Fair enough.  Changed.
The socket's an instance of either TCPSocket or UDPSocket when Connect() is
called.  So I figured this would let us support DTLS later (if desired).  I can
move it over to TCPSocket if preferred.

   bool is_connected_;
 
  private: