- What is the TagsLock CGI?
-
TagsLock CGI is a script to protect generated html-pages from such things as SPAM, copyrights violation, on-line theft (images, flash scripts, sounds…)
Use it to keep your financial gain! Don't allow somebody use your own Web content!
Also we recommend you to try professional desktop version for Windows — TagsLock Pro, it is a stand-alone program to protect already made pages.
- How does it works?
-
When you generate a html-page by your cgi-script, you, as rule, do it so:
...
print "Content-type: text/html\n\n";
print "<html>\n";
...
print "<h1>See the results</h1>\n";
...
print "<hr>© My comp. All rights reserved.<br>\n";
print "All question to <a href=mailto:webmaster\@site.com>
webmsater</a>";
...
or so:
...
print <<'ENDIT';
-- web page content here --
ENDIT
In the most of generated pages you point e-mail addresses, links to another sites and other info. TagsLock CGI library offers some good function to help you hide some info from cyber-cheaters. It work using javaScript and CGI technology. Now ~100% of browsers support this technology, so it is safe for your site.
Just little example, how to hide e-mail address from spammers's tool to extract e-mails (see also question #12):
was:
print "Please mail <a href=mailto:sales\@site.com>here</a>
to get more info about sales\n";
using TagsLock CGI:
print "Please mail", tlp_crypt_email("sales\@site.com"), " to get more info about sales\n";
So it is very simple in use and you will do a little changes.
- Where can/must I use this program?
-
TagsLock CGI is a Perl-script. So it must be used in any environment where Perl interpreter can be found. So we developed this script in Windows 98 SE and Perl ver. 5.003_7 build 316. After it was tested in Linux RedHat 7.0 with its Perl. Also it successfully worked in some other Web sites.
- What are minimal system requiriments?
-
Very little: Perl 5 and 50-100 Kb of disk space.
- How can I protect only e-mails in my site?
-
It depends from a way how you generate html-page.
If you do it with 'print' functions, you can do it so:
was:
print "<a href=mailto:mail\@isp.com>e-mail addr</a>"
now:
print tlp_crypt_email("mail\@isp.com", "e-mail addr");
or so:
print tlp_crypt_email_mouse("mail\@isp.com", "e-mail addr");
or even so:
print tlp_crypt_email_active("mail\@isp.com", "e-mail addr");
As you see we have 3 methods to protect e-mail addresses on your site from spammer's tools to extract e-mails. Here 2 first methods use javaScript technology, last method also use CGI (don't forget to place tlp_mailto.pl to cgi-bin/ in this case).
You can use any way to protect by your kind.
If you generate html-page to a file (or you get the body of a page from file) you can protect e-mails so:
tlp_crypt_file_links("page.htm","crypted_page.htm",1)
In last case in a file "page.htm" all e-mail links will be encrypted and result will be placed to "crypted_page.htm". 1 means what only e-mail links will be protected (not all hrefs).
- How can I block off-line explorers?
-
ALL off-line explorers can be blocked with TagsLock CGI. Just see to next sample to understand it:
was:
print "go <a href=/cool_pics_87/index14.htm>here too see cool pics</a>";
now:
print "go ", tlp_crypt_link("/cool_pics_87/index14.htm", "here too see cool pics");
If you generate html-page to a file (or you get the body of a page from file) you can protect e-mails so:
tlp_crypt_file_links("page.htm","crypted_page.htm",0)
In this case a file "page.htm" will be encrypted and result will be placed to "crypted_page.htm". 0 means what all links will be protected (not only e-mail links as last one).
So you see how easy to do it!
- I want to make the source of my html-page unreadable. How?
-
It is easy again! If you already have a html-file, call next function:
tlp_crypt_file("file.htm", "newfile.htm", 1);
or:
tlp_crypt_file("file.htm", "newfile.htm", 0);
So in newfile.htm you will get unreadable for user text, protected by javaScript. But it is invisible for user in browser until he want to see the source of your page.
If you generate a page with 'print', you can do it so:
print "this is unprotected string\n";
print tlp_crypt_string("You will not read this string in html-source\n"; n");
print "this is unprotected string again\n";
So you can protect hole or not hole page. You can encrypt some string or skip another.
- How to protect my images gallery?
-
I suggest you to block right-mouse click. So surfer can't save an image. Just make next steps to do it:
...
print "<body>\n";
print tlp_misc_rm("Please use left mouse button.");
...
After it pop-up menu will be disabled and user will get an alert message when he press right mouse button.
- How can I improve my site?
-
You can insert some smart meta-tags in your page. So Search Engines will index your site better. Now there are next functions to insert meta-tags (this is a sample Perl-code):
...
print "<html>\n<head>\n<title>My page</title>\n";
print tlp_meta_discache();
print tlp_meta_expires();
print tlp_meta_allrobots();
print tlp_meta_fastrevisit();
...
I don't recommend you to use all these functions in each file, because some SE can think what you are SE-spammer and block you.
tlp_meta_allrobots()
by my mind can be used in all pages,
tlp_meta_fastrevisit
should be used in often updated pages etc.
- How to protect my site from off-line viewing?
-
TagsLock CGI can offer you a tool to protect off-line viewing of your site. Just include next code in your page:
...
print "Content-type: text/html\n\n";
print tlp_misc_off("http://www.atompark.com");
print "<html>\n<head>\n";
...
In this case when user try to view a page saved to disk, he will be redirected to http://www.atompark.com immediately.
- I found very strange error during work…
-
We strongly recommend you to test your html-pages with HTML Validators. Very often it can find hidden errors in your site. After it TagsLock CGI must do its work properly.
PS: when our programmers developed TagsLock CGI, they tested it with a big number of different pages from many popular sites. Sometimes a program caused very strange errors. Once they tried to check those pages by HTML Validator - he found errors in HTML-code there. For example some pages has next error (or feature?):
<td><a href=next_page.htm><img src=next.gif border=0></td>
There is no "</a>" here. But is works! And TagsLock CGI can fail here… in bad html-code…
So make sure what you don't have such errors!
- How to test the result?
-
Yes, you must test pages protected by TagsLock CGI. We have developed special SPAM imitator for this — E-Mail Hunter.
This program can extract e-mail addresses from your site. After protection by TagsLock CGI you can use EMH to test your site.
To estimate your site for full download ability, use Teleport Pro or same tools. See also Links.