I am going to assume that the issue was the load balancer. Please indicate if there is something else going on.
The issue with using a LoadBalancer is that they are often the termination point for the SSL connection. The LoadBalancer forwards the conversation to the WebServer/dbFront as plain, unsecure HTTP. This means that the client sees that the connection is running over SSL but dbFront and the WebServer only see HTTP which is unsecure.
One solution would be to configure dbFront to look for custom HTTP headers added by the LoadBalancer. This would need to be site specific.
Let me know if that functionality is required.