A few days ago I posted my problems that I was having with setting up a
PHP script to work with a secure server. Thought I would post a
followup to thank those who offered suggestions and possibily help
someone who has the same problem later.
One problem was that a call to
https://www.domain.dom/shop/?get=variables
wasn't pulling up the the file index.phtml but instead dropped straight
into a directory listing. Someone suggested (sorry I forget who and I
can't find the original message):
"I'm guessing that index.phtml is not include in your DirectoryIndex
directive for your SSL vhost, but is for your non-SSL vhost?
See http://httpd.apache.org/docs/mod/mod_dir.html#directoryindex";
I passed that along to the sysadmin who set up the server and sure
enough that did the trick.
The other problem was that POSTed variables wasn't being passed from
script to script. The script is written in PHP and while the problem
wasn't really a mod_ssl problem, someone may turn to this group looking
for an answer like I mistakingly did since the problem only cropped up
when using a secure url.
Basically PHP when executed looks for a file called php3.ini or php.ini
depending on the version. Failing that it looks through .htaccess for
PHP related variables. There is a variable in PHP called track_vars
which when turned on, allows variables to be passed from form to form.
What was happening was that there was no php3.ini file and so it turned
to .htaccess. When a non-secure url is used, and since there was no
track_vars in .htaccess, PHP defaults track_vars to On. During secure
connections, that same variable defaults to Off. Adding track_vars = On
to .htaccess did the trick, plus filling out a proper php3.ini file
would do it just the same.
Thanks for all the help,
Joel
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
