I've been reading these forums for a long time but never posted, so let me first say hello!
Now my problem...
I've got a client (web app) / server (java) application that uses http to transmit information. Recently I've changed from using http to https (basically for the added encryption). At first all seemed to be fine, but when testing in some alternate locations (internet connections) I was experiencing a 5 second delay before the server responded to a client request. After using TCP dump it seems that the client is initialising a connection then the server does some reverse DNS lookup against the client's name. This quite often works within a few 10's of ms and all is fine, but occasionally (from some locations) this will time out after 5s or so which then triggers everything to happen again on time. I'll post the guts of the code I'm using to establish a handler on the server side - but please let me know if I should provide more information!
Essentially I want to disable the reverse DNS lookup part of the SSL (https) connection. I don't mind implicitly trusting connections in this way at all. Any suggestions would be most welcome!
(ps - I do realise there is some DNS trickery that I could set up on my server side to sort this out, however I'd feel much more comfortable if it could be done in a line or two inside the code itself).
Thank you very much for your time,
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com