|
Posted by Malcolm Dew-Jones on 10/25/80 11:19
Andrew DeFaria (Andrew@DeFaria.com) wrote:
: This is a multi-part message in MIME format.
: --------------020109070304080007040301
: Content-Type: text/plain; charset=ISO-8859-1; format=flowed
: Content-Transfer-Encoding: 7bit
: Malcolm Dew-Jones wrote:
: > Michel (no@spam.please) wrote:
: >
: > : I don't think it particularly wise to have all .html files always
: > treated
: > : and processed as .php files. That's why I said "If you want a .html
: > file to
: > : be treated as a .php file then rename it".
: >
: > which is why I suggested that this be defined for "an area" within the
: > server.
: >
: > One reason to treat html as php might be because a site has pages that
: > have been static in the past, and they wish to enhance those pages to
: > be dynamic without breaking any existing links.
: >
: > Rewrite rules could do that to, but simply turning on php for html
: > sounds like the easiest way to do it, perhaps as a temporary measure
: > during some conversion period.
: It's the wrong way to go about it. Rename the files from .html -> .php
: and adjust the corresponding links - that's the proper way.
Hum, lets get this right, I change the name and then ask google, or any
number of other sites that link to me, to change their links.
Could you explain how that works again...
--
This space not for rent.
[Back to original message]
|