|
RCP
4.0 Users Questions Menu
|
RCP .htaccess
File List
of Categories
Page 1 Page
2
-
How can i Allow hotlinking from one folder
for banners & buttons and deny hotlinking
all my other folders & files
In the rcp htaccess file near the middle you
will find section "7" the RCP Antihotlink
code Line 2 will contains this:
/allow/hotlink/banners/ This line can be used to
allow hotlinking images from one folder only and
deny hotlinking all oher files oon your site
.... Change the path
/allow/hotlink/banners/ to a path of
a folder that you wish to you wish to use for
files that are allowed to be hotlinked :
banners, buttons ect .. Inorder to activate line
2 you must remove the: #-# === 2 things only two
things to edit in the RCP htaccess The path and
remove #-# to allow hotlinking one folder only
!!! Keep in mind ... When ever you wish to edit
any htaccess file make sure allways to use a
simple plain simple text editor and back-up,
duplicate the htaccess file before you start to
work on it .. Just in case you mess things up
easaly in this file ... Support ... If you fair
to do this yourself then feel free to email RCP
support. Send use your comments and ftp details
and were glad to do it for you ...
Top
-
RCP and the htaccess file requires
Mod_Rewrite to be ON!
AllowOverride All Yes the RCP .htaccess file is
using few required Mod_Rewrite code lines. This
requires that the module mod_rewrite is
installed and turned ON, on your website server.
On most servers it is standard enabled. If not
then clients with a dedicated server can enable
mod_rewrite them self. People with virtual
hosting accounts must contact there hosting
company and request them to turn it on for you
and also have them check if in the apache
config.file the next line is ON:AllowOverride
All. Even when mod rewrite is installed and on
with out permission for AllowOverride All it
will still not work.
Mod_Rewrite is a apache module that 90% is
standard installed on all servers. Unfortually
it is not always turned ON by default. The mod
rewrite code lines in the RCP .htaccess file
will activate the RCP scripts when needed. RCP
can not work correctly without Mod_Rewrite!
its required that mod rewrite is turned on
in the apache config file and your site has the
permission to use it all over your site. For
help or advise contact RCP support.
Top
-
Explain the use of the RCP .htaccess
file.
Next from the scripts files, themplates and
images is RCP using his own required .htaccess
file. First backup your own old .htaccess file.
Then you must replace your own htaccess file
with the RCP .htaccess or if you do not have a
.htaccess file then simply upload the RCP
.htaccess file to your web folder (same folder
that contains your index.html).
The RCP .htaccess file is part of the RCP brain.
It will activates RCP when needed. RCP will not
work without the htaccess file. The htaccess
file contains a few lines that are required and
are standard turned on. The RCP .htaccess file
contains also many other useful coding that can
be turned on by removing the #-# signals in
front of the code. It contains extra code to
stop hotlinking, stop script abuse, Custom ban
rules, stop bad sites from linking to your site
and other tricks. Each section in the .htacces
file is separated by lines and each part has his
own number. On this page we will explain the use
of each section in the .htaccess file.
Top
-
Caution is always needed with modifying
.htaccess files.
All .htaccess require caution when you modify
the code inside. Always make a backup (
duplicate) the .htaccess file before you modify
any coding. One space to mush in a code line or
one missing or wrong character can result in a
International Server Error. Wish means your
wesbite ain't loading at all. So be careful when
you edit your .htaccess file. All ways edit the
.htacces file in a plain text editor. Its always
wise to have a copy of your current working RCP
.htaccess file on your desktop or HD.
If your not sure how to turn on/off certain
parts in your RCP .htaccess file or were to
include your own code contact RCP support for
free help and advise.
Top
-
Can i add any of my own or existing coding to
the RCP .htaccess file
Yes you can ...
The bottom of the RCP .htaccess file section
(12) contains space to allow your own
coding.
Top
-
Explain the use of of the RCP .htaccess file
section (1)
Section (1) This section of your RCP
.htaccess contains the order allow, deny allow
from all coding. NO lines need to be changed
required by RCP. How ever in some cahses you
might want to deny access "Permanently"
to a given IP or Domain. Normally you should use
the RCP admin area (orange button) to add a
manually permanent IP ban. How ever if you open
the .htaccess file in a plain text editor and
type a domain or IP in the deny from
fields in section (1) it will become a permanent
ban as well. Samples:
deny from 120.65.345.34
deny from SomeDorkSite.com
If a banned visitor tries to access the
specified location they will be seeing the 403
Forbidden message or they are forwarded to your
custom Access Error Page
Top
-
Explain the use of of the RCP .htaccess file
section (2)
Section (2) This section of your RCP
.htaccess contains the by RCP required:
ErrorDocument 401. Do not change this line
unless your path to the RCP script is different
then standard provided. The second part of the
section (2) contains all your server error
document URLs. You can provide your site
visitors a different custom error page for each
error or forward them all to your index.html
page. Remove th #-# infront of the lines to
activate the coding.
Top
-
Explain the use of of the RCP .htaccess file
section (3)
Section (3) This section of your RCP
.htaccess contains by RCP required coding lines
that may not be changed or modified unless the
path to your RCP script is different then
standard provided. The coding is required by RCP
to detect and guide the hard needed search
engines visits.
Top
-
Explain the use of of the RCP .htaccess file
section (4)
Section (4) This section of your RCP
.htaccess allows you to create custom ban/trap
words for file, folder names, paths or parts of
URLs. Each word listed in section (4) is
separated by a pipe |
RCP will ban any visitor, robot, spider or
abuser for reaching a path or file or URL wish
the file name is listed in the RCP .htaccess
file section (4). Feel free to edit the standard
ban word list. You may remove or add words to
protect your site and content. Keep in mind that
each word should be separated by a pipe |
or it will result in a error. Use this
function smart as it is powerful tool to stop
hackers, file thieves, spybots and script
abusers. Nearly for anything you want to
protect.
Sample: if you wish to ban people for searching
or trying to abuse your formmail. Add the word
"formmail" to the list in section (4) of your
RCP .htaccess file. Any one requesting:
http://yourdomain.com/cgi-bin/formmail.cgi will
get banned and warned with the RCP security risk
page.
Top
-
Explain the use of of the RCP .htaccess file
section (5)
Section (5) This section of your RCP
.htaccess will prevent users from loading or
downloading file names starting with a dot like:
.htaccess or .htpasswrd. Any one trying so will
get banned.Do not modify or change the coding as
it is required by RCP any changes can result in
a error.
Top
Page 1
Page
2
|
..
|
|