Forum Moderators: travelin cat
I have heard of JavaScripts to disable the right click, but dont know is they work for Mac users. Maybe you can find one at hotscrips.com
One thing I know is once some material is published over the web, there is no bullet proof way to protect it. Some more determined users can still disable JavaScrip, copy the image adress from the code or even edit pictures out of screenshots.
The only way I know how to protect the source code of some page is to cloak it.
1. Stopping the right click doesn't stop "view source" from browser menu. In addition, by disabling "right click" you remove the visitors ability to perform many other "quick" functions (e.g. -- print, shortcut, and add to favorites and these are all good things for you).
2. "Save As/Save Target/Save Image" is also still enabled.
3. Although you can eliminate these possiblitiies as well, (such as "no bars") the visitors motive for doing such things may/or may not be what you think.
4. Copyright protection is a huge concern and also "implied", the flip side of your concern is the loss of visitors "who have no unenthical intentions" they just might be very busy, wishing to save time, save your information, so they can contact you at a later date.
Protection is best when the visitor believes you "trust" them. (for those that have enthical intentions).
A mod rewrite may help eliminate unethical behavior (serving up a blank image on "if").
The only way I know how to protect the source code of some page is to cloak it.
How does that work? Suppose you had this source code:
<html>
<head><title>AC rules</title></head>
<body><h1>AC rules</h1></body>
</html>
and you want the browser to display just that. How do you cloak that page so that the user still gets to see the intended document considering the browser can only display what is sent to it by the server?
Of course you could send this code
<html>
<head><title>AC rules</title></head>
<body><p>AC rules</p></body>
</html>
depending on the User-Agent field in the HTTP request header or the IP the request came from, but then this would be a different document.
Andreas
Always thought it was the primary goal of cloaking.
Else, I looked around for 'content protection scripts' most of them JavaScript based, so they cannot properly do the job, whathever the platform. Most of them are designed around IE for Windows and will do for the majority of visitors.
I dont know of any way to efficiently protect code offered to human visitors. Even the encription scripts dont really cut in.
If it's an image then a screenshot will always work.
I know of no browser where there's not at least a menu item called 'View Source'. If you can get at the html source, you can get hold of the the URLs for everyting that gets loaded into the page.
Images and html source gets stored in the cache. The user can just open this in Finder and take a look.
the tip from emailtools doesn't work if you use the standard one-button mouse on a mac as the code checks for a right-click - on a one-button mouse mac, right-click is replaced by click-hold, which this code doesn't detect.
you can *try* to protect images this way :
<img src="<URL>" ondrag="return false" ondragstart="return false" onmousedown="return false" oncontextmenu="return false" >
this will work in any javascript enabled browser on the mac, but if javascript is turned off you are back to square one.
yours in happy hacking
Bjarne - København ; Danmark ; Europa