Client HTTP Transport does not include values such as timeouts

[bekriebel]

With #27, the HTTP Transport was configured as a custom transport to support the TLS values. A new Transport that is created does not maintain the values of DefaultTransport and instead sets multiple values like timeouts, keepalive, and connection counts to zero values.

Since this change, I have noticed that clients that may have temporary disconnects from the push-prox proxy may have their connections break and never reestablish.

PR #45 adds the values found in http.DefaultTransport so the client acts the same as it did before. I have tested this in my environment for several days now, and it has resolved the failure to reconnect issues I was seeing.