>>23
I do not understand the overall thrust of your plan. Either SSL/TLS support is present in the library or it isn't. If it isn't, it will not magically materialize as a consequence of telling plain http to use port 443. That will just cause the other end of the connection to think that your client is spewing nonsense. If you want to add SSL/TLS functionality yourself, the amount of work involved will dwarf the entire vanilla http library. The natural first choice is to look for libwget or libcurl bindings.
I guess this isn't directly relevant to the thread, but I don't think it really warrants a thread of its own.
We have a "What are you working on?" thread for this sort of thing.