On 7/13/05, dAniel hAhler <apache-users@xxxxxxxxxx> wrote: > Thank you, Joshua. After reading it, it makes sense. > > I've now used FilesMatch to force vi backups to not been shown unparsed with: > <IfModule mod_fastcgi.c> > <FilesMatch "\.php~$"> > SetHandler php-fastcgi > </FilesMatch> > </IfModule> > > As a side note, it would make sense IMHO to add a note to the AddHandler > directive documentation about this. Well, then a note would need to be added to all the Add* directives, since they all behave the same way. Instead, we usually document these issues in common sections like the "Files With Multiple Extensions" section that I pointed you to. On an unrelated topic, why do you have the <IfModule> block? If the point is to protect against security violations by preventing unparsed php~ files being shown, then surely you would prefer the SetHandler to be present whether or not mod_fastcgi is loaded. Then if you accidentally forget to load mod_fastcgi, apache would generate an error rather than sending unparsed php. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|