* Ignacio Mas Ivars <[EMAIL PROTECTED]> [20030319 13:52 PST]: > Hi all: > > I am having a weird problem with Apache that I know must be pretty > simple to solve, but i am getting crazy with it. I have installed > apache-ssl-1.3.27 with the php4 modules... and everything is working > fine. I have downloaded bookmarker and I am trying to install, it but > all the php files have the extension php3. In theory, there should be no > problem of compatibility, but the funny thing is that i am absolutely > unable to force apache to read them as php... instead it keeps on > offering me to save them as files... I have tried to change the > extension from php3 to php and then they work, but I do not want to > change all the files... and i would like to do things right... So where > in /etc/apache-ssl/httpd.conf do I have to touch to make the php3 > extension recognized as php code?!?
You probably want something like these: # # AddType: allows you to tweak mime.types without actually editing it, or to # make certain files to be certain types. # # For example, the PHP3 module (not part of the Apache distribution - see # http://www.php.net) will typically use: # <IfModule mod_php4.c> AddType application/x-httpd-php .php4 .php3 .phtml .php AddType application/x-httpd-php-source .phps </IfModule> <IfModule mod_php3.c> AddType application/x-httpd-php3 .php3 .php AddType application/x-httpd-php3-source .phps </IfModule> # The following is for PHP/FI (PHP2): <IfModule mod_php.c> AddType application/x-httpd-php .phtml </IfModule> Which, btw, I didn't create manually. The Debian packages just did the right thing, IIRC. > > Umm, i have another second question that has been bugging me for some > time now... My server is secure... so I have it in port 443... but it > turns out that part of my family is in Spain using ADSL to connect and > Telef?nica (the operator there) has installed some funny web-caches that > make it absolutely impossible to connect to an https server... Is there > a simple way to configure Apache so that it listens to http and to https > queries and then enables the encryption only in the later case? Yes, the default mod_ssl setup does precisely this. But you're not using apache with mod_ssl, you're using apache-ssl. You can either switch to using apache with mod_ssl, or you can run 2 separate apaches: one regular apache, and one apache-ssl. You will have to maintain 2 separate config files, but not two separate content trees. It's really up to you. Personally, when building from source, I use mod_ssl. The only debian-package-based apache servers I run don't use ssl at all. -- http://www.doorstop.net/ -- "Computer Science is no more about computers than astronomy is about telescopes." -- E.W. Dijkstra
signature.asc
Description: Digital signature
