I wouldn't add anything you don't need.
Code:
## EXPIRES CACHING ##
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access 1 year"
ExpiresByType image/jpeg "access 1 year"
ExpiresByType image/gif "access 1 year"
ExpiresByType image/png "access 1 year"
ExpiresByType text/css "access 1 month"
ExpiresByType text/html "access 1 month"
ExpiresByType application/pdf "access 1 month"
ExpiresByType text/x-javascript "access 1 month"
ExpiresByType application/x-shockwave-flash "access 1 month"
ExpiresByType image/x-icon "access 1 year"
ExpiresDefault "access 1 month"
</IfModule>
## EXPIRES CACHING ##
Basically, this is a cookie expiry module. Probably left over from a script that was run on the old server. Unless you actually need to control cookies for a particular reason, this can be left out. One example of a requirement would be a sign up pop up. If the user sees the pop up and closes it, the expiry wouldn't show that pop up to them again for XX number of days. It's basically useless except in direct marketing.
Code:
<Files ~ "^\.(htaccess|htpasswd)$">
deny from all
</Files>
Options Indexes
order deny,allow
All this is doing is preventing anyone from directly accessing your .htaccss file. However, with Apache, there is no direct access anyway and most reliable servers will have this encoded in the main file on the whole server. There is no need for it.
Code:
<IfModule mod_headers.c>
<FilesMatch "\.(js|css|xml|gz)$">
Header append Vary: Accept-Encoding
</FilesMatch>
</IfModule>
Again, this is probably from the old server. GoDaddy uses FastCGI and the cache modules are already there. This forces them to run again, which can slow down the server or break your site. Either way, if it is already run, you don't need to run it again.
Code:
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
This is a compression force value for each of the file types. It is used to speed up load times of your site for the client side (visitors). Unless you are running HUGE amounts of scripting and server side cache, implimentation and other such things, the compression won't really matter much. You may leave this out and only suffer a few miliseconds of laod time, which isn't enough to kick anyone off your site because images and scripts aren't loading.
Code:
AddType audio/ogg .oga
AddType video/ogg .ogv
AddType application/ogg .ogg
AddHandler application-ogg .ogg .ogv .oga
This allows your site to process and play .ogg files which are native to Linux. The Vorg Obb file format is similar to .wav for windows. If you aren't posting any .ogg files, there isn't a need to have this either. If you are, there are better ways to display them (and you should have mp4 and mp3 back ups running anyway).
If nothing is broken, I would suggest you just leave it as is. Bloat isn't needed.
Bookmarks