You can set when cache expires by Seconds, Minutes, Hours, Days, Weeks, Months, and Years.  You can set a default expires date, by using ExpiresDefault
For example “ExpiresDefault 1 month”  would set the default expiration of cache to be one month from now.

To add expires header to all of the images, Javascript, and CSS files, you can use the following code in a .htaccess file
<FilesMatch “\.(ico|jpg|gif|png|jpeg|js|css|swf)$”>
ExpiresDefault “access plus 2 weeks”
</FilesMatch>

The above code will cache the file types listed for 2 weeks before the browser will try to get new ones.

One thing to keep in mind with this however is that the browser will not check for updates until the cache expires.  So you’ll want to be careful with the file types you are setting this on, as well as how long you are setting it.  For example, if you have a .jpg file that you change every few days, then you should not set the expires headers to 2 weeks.  It should only be a day or 2.

You can specify individual files like this in a .htaccess

ExpiresActive On
ExpiresDefault A0
ExpiresByType image/jpg A604800

The default is set to 0 seconds, so everything would expire right away.  The jpg is set to 1 week.
A604800 is one week in seconds (60*60*24*7)
The “A” in the timestamp is required.  It means to expire from the date it was viewed.  Alternatively, you can swap the “A” for an “M”.  An “M” Means from the time the file was last modified.

The post Add far future expiry header to your site first appeared on Server Sitters.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

The above is the default wordpress .htaccess file.  And should help to troubleshoot if anything in your own is wrong.

The post A properly formated wordpress htaccess first appeared on Server Sitters.

If https is not on, then rewrite the url to https

RewriteEngine On
RewriteCond %{HTTPS} !^on$
RewriteRule (.*) https://yourdomain.com/$1 [R,L]

If the site is not loaded on port 443, then rewrite to the url to https:

RewriteEngine On
RewriteCondition %{SERVER_PORT} !^443$
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]

If the site is loaded on port 80, then rewrite the url to https:

RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]

The post Force http to redirect to https via a .htaccess file first appeared on Server Sitters.

Parse error: syntax error, unexpected T_STRING in /home/username/public_html/index.html on line 1
To correct this, you need to turn short_open_tags off in PHP.

Here are 2 ways to do this:

.htaccess

php_flag short_open_tag off
— OR —
php_value short_open_tag 0

PHP.INI

Find the line that says short_open_tag in php.ini and turn it off

The post Unexpected T_STRING in an Apple iWeb site. first appeared on Server Sitters.

On a cPanel server, to reinstall frontpage extensions from the command line, do the following.

*** Note this is destructive

• SSH to the server the customer is on.
• cd ~theirusername/public_html
• find ./ -iname '_*' -print0 | xargs -0 rm -Rf
• find ./ -iname '.htaccess' | xargs rm -f
• find ./ -iname '*.lck' | xargs rm -f
• rm /usr/local/frontpage/$domainname.com*
• rm /usr/local/frontpage/www.$domainname.com*

These commands delete all folders starting with an underscore (_), all .htaccess files, and all files with an extension of .lck.  It then deletes the server configuration files for frontpage itself for the domain.  Once these have been deleted, frontpage has been fully removed from the server.

To re-install frontpage, run this command.

• /scripts/setupfp5 $domainname.com

Depending on the size of this site, this can take a few seconds, or several hours.  Once completed, the customer will need to re-publish the site and/or recalculate hyperlinks.

The post Manually re-install FrontPage Extensions first appeared on Server Sitters.

The post Apache Handlers first appeared on Server Sitters.


SetEnv PHPRC /home/$user/public_html/php.ini


Then a php.ini file with:
auto_prepend_file = /home/$user/public_html/checkrefer.php

checkrefer.php


<?php
session_start();
echo $_SESSION['allowme'];

//First we check to see if a valid session exists
if ($_SESSION[‘allowme’]==1){
//keep going and allow access
}
else {
$domain=$_SERVER[“HTTP_REFERER”];
$domainref = parse_url($domain, PHP_URL_HOST);
//check to see what the referrer is
if ($domainref==”$validreferdomain”){
//start session and allow access
$_SESSION[‘allowme’] = 1; // store session data
}

//block access bad referrer and no session
else{
print “Access Forbidden. Please visit this page for further information.”;
exit;
}

}
?>

On this script you have to set $validreferdomain = to the referrer you want the visitor to come from.

Limitation – this only effects php pages and not images or other file types. You can get it to lock down html pages by setting the site to parse html as php.

The post Limit access to website based on referrer first appeared on Server Sitters.

The post Disable directory indexing first appeared on Server Sitters.

The post Disable Zend using a .htaccess file first appeared on Server Sitters.

Options +ExecCGI

The post Setting CGI to execute outside cgi-bin first appeared on Server Sitters.