htaccess AddType question

[nate]

Originally Posted by cd34

<FilesMatch "\.htm(l)?$">
    SetOutputFilter INCLUDES
</FilesMatch>
AddType application/x-httpd-php .htm .html

Ewwwwwww.

echo @stripslashes( @join( @file( "http://www.somedomain.com/cgi-bin/someperl.cgi" ),"" ));

As for running htm pages as php, maybe in one directory it would be OK, but not sitewide. You dont really want HTM being parsed as PHP if you can help it. It will cause a performance hit.

[ponygirl]

Originally Posted by cd34

<FilesMatch "\.htm(l)?$">
    SetOutputFilter INCLUDES
</FilesMatch>
AddType application/x-httpd-php .htm .html

Originally Posted by nate

echo @stripslashes( @join( @file( "http://www.somedomain.com/cgi-bin/someperl.cgi" ),"" ));

ok you two, get a room

well I'm not up on all this techy stuff lol. If you tell me how to do something I'll understand it, but I probably won't know why it works

I have one directory with about 125 or so pages that I'd be needing the php on. Any new pages in that directory I would just do as php I guess.

I was thinking about just switching them to php anyway if I can do a global redirect or something since they're all in the same directory? I really don't want to have to redirect 125 pages separately, it sounds a bit messy.

for now I'm going to parse 'em, if you guys have a good solution my ears are open

[cd34]

Originally Posted by ponygirl

I have one directory with about 125 or so pages that I'd be needing the php on. Any new pages in that directory I would just do as php I guess.

I was thinking about just switching them to php anyway if I can do a global redirect or something since they're all in the same directory? I really don't want to have to redirect 125 pages separately, it sounds a bit messy.

personally, I would leave them as .htm or .html files and just parse them. No supported evidence behind it, but, a gut feeling that google prefers .html files over .php

If you wanted to redirect files, you could do it with mod_rewrite.

If you want to silently serve the .php as .html (and for some reason didn't want to parse .html)

RewriteEngine on
RewriteRule ^(.*).html$ $1.php [L]

If you wanted to 301 redirect the old content to the new page

RewriteEngine on
RewriteRule ^(.*).html$ $1.php [R=301,L]

Personally, I would just turn on php parsing for .html files in that directory and not worry about it.

[ponygirl]

Originally Posted by cd34

personally, I would leave them as .htm or .html files and just parse them. No supported evidence behind it, but, a gut feeling that google prefers .html files over .php

If you wanted to redirect files, you could do it with mod_rewrite.

If you want to silently serve the .php as .html (and for some reason didn't want to parse .html)

RewriteEngine on
RewriteRule ^(.*).html$ $1.php [L]

If you wanted to 301 redirect the old content to the new page

RewriteEngine on
RewriteRule ^(.*).html$ $1.php [R=301,L]

Personally, I would just turn on php parsing for .html files in that directory and not worry about it.

thank you |blowkiss| that's exactly what I want to do because it seems to be the easiest way.

[LD]

Originally Posted by cd34

personally, I would leave them as .htm or .html files and just parse them. No supported evidence behind it, but, a gut feeling that google prefers .html files over .php

If you wanted to redirect files, you could do it with mod_rewrite.

If you want to silently serve the .php as .html (and for some reason didn't want to parse .html)

RewriteEngine on
RewriteRule ^(.*).html$ $1.php [L]

So if you wanted a "page.php" to display as "page.html" to perhaps take advantage of Google's hypothetical preference, this would work?

Interesting thread...wish I understood more of this stuff...

[cd34]

Originally Posted by nate

echo @stripslashes( @join( @file( "http://www.somedomain.com/cgi-bin/someperl.cgi" ),"" ));

realizing of course that if maxclients is set to 512, and you have 257 surfers hitting a page that is calling that url from your local server, you're going to get a connection refused on the 257th surfer's request. Since php doesn't support keepalives, do that more than once on a page and you've got 1+ a connection for each of the file requests, reducing the number of surfers that you can serve on your site.

And that doesn't really solve the problem. If a file is being included, sure, that will work, though,

echo @file_get_contents('http://www.somedomain.com/cgi-bin/someperl.cgi');

is a bit friendlier, and, honors the timeout timer built into php. file, if I recall, does not honor the default_socket_timeout. Neither does include/include_once or require/require_once.

If it is a local file, you're better off doing:

echo @file_get_contents('/path/to/localfile.html');

But, how do you handle normal SSI?

        <!--#config timefmt="%A %B %d, %Y" -->
        Today is <!--#echo var="DATE_LOCAL" -->

Without converting that code to php, you would have to add the output filter for INCLUDES. SSI is used for more than including other files including adding the query string to urls, displaying the current date, etc.

In the end, SSI wasn't used, so, it's a moot point.