The only way you could do something like that would be to develop your own custom display plug-in that could decrypt/display the page. Frankly, any decryption that takes place on the end-user's host is subject to reverse engineering anyway, so I would recommend you don't even bother.

1. This is not a Perl issue.
2. What do you have to hide? What's so secret?
3. Think about it, if the HTML was encrypted, how would a browser display it?

Abigail

What you are asking is unfeasible, due to the client server protocol in web interface. For the browser to display the page, the server must send it in readable mode, anyway in a format understandable for a browser.

Everything the web server sends in such format can be read by any program that knows what to expect from a server. You can fool a dumb browser, but nothing can prevent somebody with Perl and LWP from seeing what the server is sending.

See also html tag encryptor/decryptor for a discussion on the same subject.

It is possible, you must create a new kind of browser, that doesn't allow operations like cut'n'paste, save and print. That browser should also be the only allowed to communicate with your web server... It doesn't seem a practical approach, does it? A solution based on some javascript trick will not stop smart users; the only feasible, but far from good solution is to use Flash everywhere... but a pencil and a sheet of paper will still work :)

Can you explain us why you need to protect content of your pages? Can't you use a different approach?

Ciao, Valerio

Once the page on the client-side the browser, it's not Perl's problem. It's HTML and JavaScript problem.

You can use JavaScript to disable right click, which's breakable, however. In IE, I think it is:

function click(){
   if (event.button==2){
      alert("Oops, you can't do that.");
      return false;
   }
}
[download]

The code is different in Netscape.

You could also hide your HTML in a JavaScript file, so when view source people will see the links to the javascript files, not the content.

In the first solution, a knowledgeable user can turn off javascript to get around the "fix".

--Bob Niederman, http://bob-n.com

A 'knowledgable user'?? I wish I could have some of those..

For the second solution, it just adds another layer of indirection. That extra JavaScript page must be publically viewable, and anyone smart enough to look at the source should be smart enough to copy-and-paste the link.

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

Note: All code is untested, unless otherwise stated

Inspite of this post drag many negative points to my small reputation i thank you all for your advices and for making me understand that this is not the best way!!

Thank you all!

You might also want to consider that people without javascript (like me) see a blank window when they access your page. I don't know what to what end you are trying to do this, but keep in mind that at least some of the people who visit your site will see nothing at all.

</ajdelore>