Include secure file from non-secure page - bad or good idea?
Posted: Tue Jun 12, 2007 11:01 am
Hi,
I have a file containing various database functions that up until now has only been used (accessed) on the secure (https) part of my site. Now, I need to access it from the regular http part of the site. However, when I try to include the file in the form:
include ("https://www.mysite.com/dbfile.php")
I get the "failed to open stream" warning and then a fatal error. I am assuming that it has something to do with the include_path settings in httpd.include. However, my question is whether it is a good idea to include a secure file from a non-secure page in the first place. Is it?
Thanks.
I have a file containing various database functions that up until now has only been used (accessed) on the secure (https) part of my site. Now, I need to access it from the regular http part of the site. However, when I try to include the file in the form:
include ("https://www.mysite.com/dbfile.php")
I get the "failed to open stream" warning and then a fatal error. I am assuming that it has something to do with the include_path settings in httpd.include. However, my question is whether it is a good idea to include a secure file from a non-secure page in the first place. Is it?
Thanks.