Problems Using an Access Database with Shared SSL

Calling a page in the shared SSL folder should normally not affect an ODBC DSN based connection string or other database code. In most cases the same ASP code should work unchanged between SSL and non-SSL pages.

If you are using a DNS-less connection and the Access database is located outside your secure folder you will need to either hard-code the database location or convert to an ODBC DSN.

Another common problem when using our Shared SSL Certificate and a database is the fact that session and application variables are not retained between the secure and non-secure environments. If you first establish a connection in the non-secure environment and/or set other sessions or application variables, this does not get inherited by the secure session.

To retain session and application settings between HTTP and HTTPS, you need your own SSL certificate mapped to your site. Our shared certificate cannot provide seamless transitions that retain such settings.

To mimic a seamless transition between secure and non-secure environments, you will need to transfer state information by methods other than session or application variables. Common methods include using a database or file to store information gathered non-securely, then retrieve it in the secure environment from an ID passed on the query string or form. Also, you can use hidden form variables or other query string data to transfer transactional information to the secure environment.

If the above information does not help with a current problem, can you direct us to a page giving you trouble? We can then have a quick look at the code you are using and may give us a better idea as to how to solve your problem.

For more information about purchasing and installing an SSL Certificate, please visit:

Add Feedback