Adds hostname verification to the vertx DefaultHttpClient, along with accessors to disable it.  Hostname verification is an essential part of the HTTPS specification (rfc 2818 - http://tools.ietf.org/html/rfc2818#section-3.1).  Without it, vert-x is fundamentally insecure and open to man-in-the-middle attacks as clearly explained/substantiated in this article:  "The most dangerous code in the world: validating SSL certificates in non-browser software" (https://crypto.stanford.edu/~dabo/pubs/abstracts/ssl-client-bugs.html).

The fix adds hostname verification by adding the "HTTPS" endpoint identification algorithm to the SSL parameters if SSL is enabled on the client.  Note that creating the SSLEngine object now takes the request host and port; this is really only a requirement if hostname verification is enabled, but I didn't see any harm in including it for all SSL cases.
fix coding mistake:  change "isVerifyHost" to "setVerifyHost"
classloader changes
classloader changes
add hook to allow external handling of connection in SockJSServer
EventBusBridgeHook and example
Merge remote-tracking branch 'upstream/master'
Update vertx-core/src/main/java/org/vertx/java/core/http/impl/DefaultHttpServerResponse.java

fix multiple Set-Cookie headers issue
Update vertx-core/src/main/java/org/vertx/java/core/http/impl/DefaultHttpServerResponse.java

avoid multiple getValue() invoke (base on previous modification)
UGLY: return multiple Set-Cookie headers
add testMultipleSetCookieHeaders
allow multiple headers with same name in trailer
move test code from JavaHttpTest to HttpTestClient
calling unregister hook before disconnect handler on sockjs socket close
upped version number and various other fixes and tweaks
https hostname verification
Merge pull request #481 from winash/master

Call Unregister hook before sockjs disconnect
More effective sharing of conenctions in the HttpClient connection pool
More effective sharing of conenctions in the HttpClient connection pool
a few tweaks prior to release