http://www.savagehost.com/how-do-i-hide-the-file-extinsion-on-the-end-of-my-domain-name.html Just another WordPress weblog Tue, 02 Mar 2010 23:13:58 -0600 http://wordpress.org/?v=2.8 hourly 1 http://www.savagehost.com/how-do-i-hide-the-file-extinsion-on-the-end-of-my-domain-name.html/comment-page-1#comment-11931 whatever Tue, 24 Nov 2009 07:44:48 +0000 http://www.savagehost.com/how-do-i-hide-the-file-extinsion-on-the-end-of-my-domain-name.html#comment-11931 You could change your .htaccess file to hide or change the extension of your index.html files. You could change your .htaccess file to hide or change the extension of your index.html files.

]]> http://www.savagehost.com/how-do-i-hide-the-file-extinsion-on-the-end-of-my-domain-name.html/comment-page-1#comment-11930 Ron Tue, 24 Nov 2009 07:23:36 +0000 http://www.savagehost.com/how-do-i-hide-the-file-extinsion-on-the-end-of-my-domain-name.html#comment-11930 Maybe you should make a new folder with your ftp client or through the file manager in your cPanel and call it news in the public_html folder. Then what you'd have to do is upload the thing that you would normaly call news.htm into the news folder except you have to call it index.htm good luck :) Maybe you should make a new folder with your ftp client or through the file manager in your cPanel and call it news in the public_html folder. Then what you’d have to do is upload the thing that you would normaly call news.htm into the news folder except you have to call it index.htm
good luck

]]> http://www.savagehost.com/how-do-i-hide-the-file-extinsion-on-the-end-of-my-domain-name.html/comment-page-1#comment-11929 Ron Tue, 24 Nov 2009 01:32:00 +0000 http://www.savagehost.com/how-do-i-hide-the-file-extinsion-on-the-end-of-my-domain-name.html#comment-11929 First, remove "index.html" from the links on all of your pages. It is the links on your pages which determine the url, while internal rewrites (including Directroyindex) associate a "Web" url with a server filepath. Then redirect only client requests for "/index.html" to "/". This restriction is necessary to prevent a loop, since Directoryindex will rewrite "/" back to "/index.html" and if you overlook it, you'll create an 'infinite' redirect/rewrite loop. RewriteCond %{THE_REQUEST} ^[A-Z]{3,9} /tagword/([^/]+/)*index.html RewriteRule ^tagword/(([^/]+/)*)index.html$ http://www.example.com/tagword/$1 [R=301,L] Both steps are required to "change" a url and get the search engines to drop the old one. THE_REQUEST is the HTTP request header as received from the client (browser or 'bot), and might look like this: GET /tagword/main/sub/index.html HTTP/1.1 Ron First, remove “index.html” from the links on all of your pages. It is the links on your pages which determine the url, while internal rewrites (including Directroyindex) associate a “Web” url with a server filepath.
Then redirect only client requests for “/index.html” to “/”. This restriction is necessary to prevent a loop, since Directoryindex will rewrite “/” back to “/index.html” and if you overlook it, you’ll create an ‘infinite’ redirect/rewrite loop.
RewriteCond %{THE_REQUEST} ^[A-Z]{3,9} /tagword/([^/]+/)*index.html
RewriteRule ^tagword/(([^/]+/)*)index.html$ http://www.example.com/tagword/$1 [R=301,L]
Both steps are required to “change” a url and get the search engines to drop the old one.
THE_REQUEST is the HTTP request header as received from the client (browser or ‘bot), and might look like this:
GET /tagword/main/sub/index.html HTTP/1.1
Ron

]]>