You might be able to create a modified XBitHack Apache module which,
essentially checks to see if the a file has the "x" (execute) bit set
under permissions. If so, then it parses the file, if not, then it
displays as a regular html file. This is normally used for server side
includes, but you
On Sep 2, 2007, at 7:02 AM, Elliotte Harold wrote:
Suppose I don't want it to be so obvious that I'm using PHP on a
site, Or that I just want the freedom to not always use PHP in a
given document. Thus I decide to configure Apache to treat
all .html files as PHP files.
How much overhead
Elliotte Harold wrote:
Suppose I don't want it to be so obvious that I'm using PHP on a site,
Or that I just want the freedom to not always use PHP in a given
document. Thus I decide to configure Apache to treat all .html files as
PHP files.
How much overhead does this add for the common case
Josh McCormack wrote:
You could get around having to have all pages be php by running
through some sort of preprocessos that makes static pages for that
audience, day, hour, etc, and flags which files really need to be
dynamic. Sounds like a lot of work, though.
Josh
I'm currently building
You could get around having to have all pages be php by running
through some sort of preprocessos that makes static pages for that
audience, day, hour, etc, and flags which files really need to be
dynamic. Sounds like a lot of work, though.
Josh
On 9/2/07, David Krings <[EMAIL PROTECTED]> wrote
Elliotte Harold wrote:
Suppose I don't want it to be so obvious that I'm using PHP on a site,
Or that I just want the freedom to not always use PHP in a given
document. Thus I decide to configure Apache to treat all .html files as
PHP files.
How much overhead does this add for the common case
Elliotte Harold wrote:
Suppose I don't want it to be so obvious that I'm using PHP on a site,
Or that I just want the freedom to not always use PHP in a given
document. Thus I decide to configure Apache to treat all .html files
as PHP files.
How much overhead does this add for the common case
Suppose I don't want it to be so obvious that I'm using PHP on a site,
Or that I just want the freedom to not always use PHP in a given
document. Thus I decide to configure Apache to treat all .html files as
PHP files.
How much overhead does this add for the common case when a file only
conta
