|
|
Page Guard Pro installation documentationHelp for setting up the Page Guard Pro script.
Version Program Name : Page Guard Pro Version : 1.0 Last Modified : 20 Mar 2008 Made : Hand made top Features Script replace the nasty looking error pages. Explain the web error to the visitor in a web page. Send email to your administrator with the web error info. Logs the web errors. Custom header and footer. And much more......... top System Requirements A unix (linux) web server. Perl Version 5 or higher. A web server that is compatible with Apache version 1.3 or higher (most are). A web page that allows custom CGI. The ability to write custom .htaccess files. A program on the web server like sendmail. top Installation and Configuration Open the admin.cgi and guard.cgi files with your favorite text editor. And look for the line. #!/usr/local/bin/perl If needed change the path to Perl. Make a directory in your cgi-bin directory something like guard-pro. Upload everything in the same context to your /cgi-bin/guard-pro directory. Upload everything in ASCII mode except the images upload the images in BIN mode (be sure of that other why the script is not working) Note : For the Windows users. Auto detect is many times not good working. top Files and Permissions /cgi-bin/guard-pro directory chmod 755 /cgi-bin/guard-pro/html directory chmod 777 /cgi-bin/guard-pro/log directory chmod 777 /cgi-bin/guard-pro/members directory chmod 777 /cgi-bin/guard-pro/images directory chmod 777 admin.cgi file chmod 755 guard.cgi file chmod 755 top Main Config Open the main.cfg file with your favorite text editor. follow the instructions in the file. open the admin.cgi and look for the lines. $username="root"; $password="roots"; Change it in your user name and password top Setting up Custom Error Pages Make a text file named .htaccess, put the lines below in it and upload it in the main directory. For the windows users a make a file like member.htaccess, upload it to the server and rename it in .htaccess ErrorDocument 301 /cgi-bin/guard-pro/guard.cgi?301 ErrorDocument 302 /cgi-bin/guard-pro/guard.cgi?302 ErrorDocument 401 /cgi-bin/guard-pro/guard.cgi?401 ErrorDocument 402 /cgi-bin/guard-pro/guard.cgi?402 ErrorDocument 403 /cgi-bin/guard-pro/guard.cgi?403 ErrorDocument 404 /cgi-bin/guard-pro/guard.cgi?404 ErrorDocument 500 /cgi-bin/guard-pro/guard.cgi?500 ErrorDocument 501 /cgi-bin/guard-pro/guard.cgi?501 Were is /cgi-bin/guard-pro/guard.cgi the URI to your guard.cgi (not the full URL). This script can use all the error codes All the possible error codes I now are. 100 => 'Continue', 101 => 'Switching Protocols', 200 => 'OK', 201 => 'Created', 202 => 'Accepted', 203 => 'Non-Authoritative Information', 204 => 'No Content', 205 => 'Reset Content', 206 => 'Partial Content', 300 => 'Multiple Choices', 301 => 'Moved Permanently', 302 => 'Moved Temporarily', 303 => 'See Other', 304 => 'Not Modified', 305 => 'Use Proxy', 400 => 'Bad Request', 401 => 'Unauthorized', 402 => 'Payment Required', 403 => 'Forbidden', 404 => 'Not Found', 405 => 'Method Not Allowed', 406 => 'Not Acceptable', 407 => 'Proxy Authentication Required', 408 => 'Request Timeout', 409 => 'Conflict', 410 => 'Gone', 411 => 'Length Required', 412 => 'Precondition Failed', 413 => 'Request Entity Too Large', 414 => 'Request-URI Too Large', 415 => 'Unsupported Media Type', 500 => 'Internal Server Error', 501 => 'Not Implemented', 502 => 'Bad Gateway', 503 => 'Service Unavailable', 504 => 'Gateway Timeout', 505 => 'HTTP Version Not Supported', top Tracking the Good Logins There are two way for to track the loggings on your page. If you have SSI (Server Side Include) enabled on you web page than is the SSI (Server Side Include) call the best way for you. You can than track multiple password protected directory's at on time If you are not so lucky that have SSI (Server Side Include) enabled on you web page than is the Image call the best way for you. You can than track only one password protected directory at on time, with one script. And the guard.cgi must be in the same directory where the password protected directory is. For the use of the SSI (Server Side Include) call you have to call the guard.cgi on your members page as an SSI call. Like: <!--#exec cgi="/cgi-bin/guard-pro/guard.cgi" -->For the use of the Image call you have to call the guard.cgi on your members page as an image. Like: <img src="/cgi-bin/guard-pro/guard.cgi">Where /cgi-bin/guard-pro/guard.cgi is the URI to your guard.cgi. Not the full URL. If http://widexl.com/cgi-bin/guard-pro/guard.cgi is the full URL to the guard.cgi Then is the URI /cgi-bin/guard-pro/guard.cgi The guard.cgi must be in the same directory where the password protected directory is. top Copyright Information Copyright © 2000. Henk Boonstra. All Rights Reserved. This Version is a Freeware release. It is free to use for particular purpose, non-profit and commercial organizations. You can change or modify this script if as you want it. However, modified versions cannot be sold or distributed. You cannot alter the copyright and "powered by" notices throughout the scripts. These notices must be clearly visible to the end users. By using this program you agree to conditions above. top Warranty Disclaimer THIS PROGRAM IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL, BUT WITHOUT ANY WARRANTY. WITHOUT EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
» Keyword Ranking |
| Copyright © 2000-2008 Widexl |