HTML encryption issues [FAQ]

html encrypt source code Protect HTML.Encrypt files partially - can I do this?
Yes. You need to use the partial encryption option. Since this option is not available in HTML Guardian's main window, many users get confused. HTML Guardian can encrypt either an entire file, or only desired parts of it.
If you want to encrypt a part of the code, you have to enclose it within these html comment tags (case sensitive):

<!--htmlgstart -->
... here comes the part of the code you want to encrypt
<!--htmlgstop -->

If you want some part of the code to remain unencrypted, you have to enclose it within these html comment tags(case sensitive):

<!--htmlgskipstart -->
... here comes the part of the code you do not want to encrypt
<!--htmlgskipstop -->

Note: There should be no empty space after <!-- and there should be one empty space before --> - otherwise the tags will not be recognized.
If HTML Guardian founds these tags in the file to be encrypted, it will automatically switch to partial encryption mode, otherwise it will encrypt the entire file. Partial encryption is only possible for html files, and not for script, frameset, .shtml or .asp files. You can encrypt or leave unencrypted as many parts of the code as you wish, but you can't mix both partial encryption methods in one file.
Partial encryption can be very useful sometimes. This way you can edit the unencrypted code without having to reencrypt the file afterwards. Also you can use it for big html files, like 100K or bigger - decoding the encrypted code can be slow for big files if your visitors use slow processors, like 486 or slower.
You can also use the partial encryption to skip problematic parts of the code and leave them unencrypted. For example some webpage visit counters code may cause problems - just mark this code to be skipped.
Parts of the code selected for encryption or for skipping should not contain unclosed tags, otherwise in some cases files may not be displayed properly. Example:

Correct
Incorrect
<!--htmlgstart -->
<table>
...........
</table>
<!--htmlgstop -->
<!--htmlgstart -->
<table>
...........
<!--htmlgstop -->
</table>


Go Back


Can I encrypt HTML formatted email messages?
Yes, you can. However, there could be problems if the html encrypt file you want to send as an email uses external files (such as images, external script files or java applets, or external style sheets). For style sheets and scripts , just include their content in the html code rather than using external files. For images it is harder, the only way to send html encrypted file with images inside is to make the images available on the web. So your <IMG... > tags should look like this before encryption:
<IMG src = "http://www.domain.com/pictures/image1.jpg">
This is because of the way external files are handled when you send html(encrypted) formatted e-mail.
Go Back


Can I disable copy text command in my pages?
Yes. Tick the 'Disable text selection' checkbox. This will make impossible to select text and copy it by dragging the mouse, pressing Ctrl+A or clicking 'Select All' either in browser's 'Edit' menu or in the right-click context menu (or in any other way).
Go Back

Can I disable printing on my website?
Yes. You should check the 'Disable page printing' box.
Note that this will not actually 'disable' printing. When someone tries to print a protected html file, only blank pages will be printed (having only header or footer, but no content).

Go Back

If I encrypt HTML source, can it be edited with html editors?
No, it is not possible to edit the html encrypted source in such programs. Of course you can modify the source in text editors like Notepad, but changing even a single character in the encrypted code will result in a non-working file. When you encrypt HTML code, any WYSIWYG editors like DreamWeaver or FrontPage will not be able to see it - protection will hide HTML source of the original file from all programs.
Actually if you encrypt html,protect it or secure it in any way with HTML Guardian, protected source can't be edited at all.

Go Back

Go back Next

   © 1997-2005, ProtWare Inc. All rights reserved.