<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Using .htaccess to Parse HTML Files as PHP</title>
	<link>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/</link>
	<description>Ask the Windows Guru!</description>
	<pubDate>Sat, 04 Feb 2012 12:03:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Nilpo</title>
		<link>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-131550</link>
		<dc:creator>Nilpo</dc:creator>
		<pubDate>Mon, 07 Feb 2011 16:36:24 +0000</pubDate>
		<guid>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-131550</guid>
		<description>While it is true that the PHP parser is invoked, the parser exits immediately if there are no PHP tags.  Nonetheless, this is all a moot point.  The idea behind this is that you WANT the files to be parsed as PHP so that PHP content can be named with an HTML file extension.  The files themselves are, in fact, PHP files.  If the PHP parser were not invoked, you wouldn't be serving any pages at all.</description>
		<content:encoded><![CDATA[<p>While it is true that the PHP parser is invoked, the parser exits immediately if there are no PHP tags.  Nonetheless, this is all a moot point.  The idea behind this is that you WANT the files to be parsed as PHP so that PHP content can be named with an HTML file extension.  The files themselves are, in fact, PHP files.  If the PHP parser were not invoked, you wouldn&#8217;t be serving any pages at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fiable.biz</title>
		<link>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-131548</link>
		<dc:creator>Fiable.biz</dc:creator>
		<pubDate>Mon, 07 Feb 2011 16:15:13 +0000</pubDate>
		<guid>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-131548</guid>
		<description>Thank you for your quick answer.

I think it's not a good idea for the reason explained there in the "note of warning":
http://www.electrictoolbox.com/apache-parse-html-as-php/</description>
		<content:encoded><![CDATA[<p>Thank you for your quick answer.</p>
<p>I think it&#8217;s not a good idea for the reason explained there in the &#8220;note of warning&#8221;:<br />
<a href="http://www.electrictoolbox.com/apache-parse-html-as-php/" rel="nofollow">http://www.electrictoolbox.com/apache-parse-html-as-php/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nilpo</title>
		<link>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-131545</link>
		<dc:creator>Nilpo</dc:creator>
		<pubDate>Mon, 07 Feb 2011 15:57:14 +0000</pubDate>
		<guid>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-131545</guid>
		<description>This method is not brutal at all.  In fact, it's a pretty standard practice.  The parser is only going to parse files which contain PHP tags.  Everything else is going to be pushed through anyway.  I guess I'm not sure why you think this is a bad idea.</description>
		<content:encoded><![CDATA[<p>This method is not brutal at all.  In fact, it&#8217;s a pretty standard practice.  The parser is only going to parse files which contain PHP tags.  Everything else is going to be pushed through anyway.  I guess I&#8217;m not sure why you think this is a bad idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fiable.biz</title>
		<link>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-131510</link>
		<dc:creator>Fiable.biz</dc:creator>
		<pubDate>Mon, 07 Feb 2011 13:40:31 +0000</pubDate>
		<guid>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-131510</guid>
		<description>Hello.

Thank you but this method is very brutal. Does is have any drawback is some .html or .xhtml pages does not contain any PHP?
Isn't it possible to say to Apache to serve some specified HTML or XHTML pages as PHP?</description>
		<content:encoded><![CDATA[<p>Hello.</p>
<p>Thank you but this method is very brutal. Does is have any drawback is some .html or .xhtml pages does not contain any PHP?<br />
Isn&#8217;t it possible to say to Apache to serve some specified HTML or XHTML pages as PHP?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: business websites</title>
		<link>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-117551</link>
		<dc:creator>business websites</dc:creator>
		<pubDate>Tue, 23 Nov 2010 10:45:42 +0000</pubDate>
		<guid>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-117551</guid>
		<description>hi thanks for share</description>
		<content:encoded><![CDATA[<p>hi thanks for share</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interview de l&#8217;auteur de Crawltrack : Jean Denis Brun</title>
		<link>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-110586</link>
		<dc:creator>Interview de l&#8217;auteur de Crawltrack : Jean Denis Brun</dc:creator>
		<pubDate>Sun, 03 Oct 2010 21:52:21 +0000</pubDate>
		<guid>http://www.nilpo.com/2008/10/apache/using-htaccess-to-parse-html-files-as-php/#comment-110586</guid>
		<description>[...] du site, alors que le tag php demande soit des pages en .php, soit un paramétrage du serveur pour traiter les pages html comme du php. Pour un produit &#171;&#160;grand public&#160;&#187;, le choix du Javascript parait au première [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] du site, alors que le tag php demande soit des pages en .php, soit un paramétrage du serveur pour traiter les pages html comme du php. Pour un produit &laquo;&nbsp;grand public&nbsp;&raquo;, le choix du Javascript parait au première [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

