Protecting your Web site from prying eyes requires a server-side solution. With Kerberos authentication, users have their own usernames and passwords and access can be granted to a directory by adding the appropriate htaccess and htpassword files. But what do you do if your ISP doesn't support such means of password protection? JavaScript can offer a limited amount of protection for just about any site. By limited protection, I mean that someone who knows what they're doing can bypass the authentication simply by view the code in most cases. So, if you need to protect anything really important, like social security numbers, company trade secrets, or charge card information, a server-based solution is the way. But, if you just want to keep the general public from viewing your Web site, JavaScript can be just the ticket. There are few scripts out there that are written for just this purpose, but most seem to have some type of drawback.Protecting your Web site from prying eyes requires a server-side solution. With Kerberos authentication, users have their own usernames and passwords and access can be granted to a directory by adding the appropriate htaccess and htpassword files. But what do you do if your ISP doesn't support such means of password protection? JavaScript can offer a limited amount of protection for just about any site. By limited protection, I mean that someone who knows what they're doing can bypass the authentication simply by view the code in most cases. So, if you need to protect anything really important, like social security numbers, company trade secrets, or charge card information, a server-based solution is the way. But, if you just want to keep the general public from viewing your Web site, JavaScript can be just the ticket. There are few scripts out there that are written for just this purpose, but most seem to have some type of drawback.