Add Non-HTTPS TCP/TLS Support

[omerlh]

Hey It is a bit unclear, so I thought it is better to ask - doest the library support also TCP/TLS connections?

Thanks, Omer

[commonsguy]

Note that this is an issue tracker. It is not a support board. I describe multiple ways of getting support in the project README.

If you are referring to non-HTTPS TCP/TLS connections, I am not sure if native network security configuration applies its rules to those or not, as I have not tried it. This backport does not, as you have to manually request that the configuration be applied, and at the moment I only offer that sort of manual configuration for a couple of HTTP APIs.

I may wind up looking into this more in mid-2017 as part of some of my own work. Otherwise, if you point me to a sample project that is using the 7.0 native network security configuration for something other than HTTPS, I can look into what would be required to support similar scenarios in this library.

[omerlh]

Ok, thank you!

[yashasvigirdhar]

The native security configuration supports non-HTTPS TCP/TLS connections. I've confirmed this in my company's project where we use a custom TCP/TLS protocol.

I'll mostly end up using this lib to support that protocol.

[commonsguy]

@yashasvigirdhar At the moment, I have no plans to try to add support for non-HTTPS in this library, mostly because I have no scenarios for it and no idea how I would convince third-party socket-based code to apply the network security configuration rules.