Hi Joshua, Thanks for the response, >> My communication from my module, is database specific (my MySQL is >> already SSL-enabled). So is it only up to the MySQL SSL-specific C API to >> provide SSL (I tried using mysql_ssl_set() with no success) or there has >> more to be done at my module's code end? > > You've so far asked this question four times, including on completely > inappropriate mailing lists, without giving people time to respond. > This type of impolite behavior makes me very reticent to even bother > replying. I really regret this. > But anyway, your problem has nothing directly to do with apache APIs. > If you want your mysql communication to be encrypted, then it is up to > your module to use the correct mysql APIs in the correct way. Apache > Has nothing to do with it. > > If you don't know how to use the mysql APIs, then I suggest you get > some help from a mysql forum. MySQL C APIs provide for enabling SSL support and they work perfect for a standalone. The APIs when used within a module is not working the expected. So what I think is, the deficit for this is somewhere at the Apache module end. Please correct me. Best Regards, Naveen Rawat --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx