The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Seriously, tell your client that what he's wishing for is impossible, but if he'd like it to be implemented, to send a cheque for $10K to Microsoft and Netscape.

I just did some research and conclude that it's nigh on impossible to prevent someone from bookmarking a page.

The best way to get around it is to use a server side language like ASP or PHP to create a cookie or authenticate a user so that the server detects whether or not a person has accessed the home page before trying to get into the login page.

(so for example, let's call the home page Page 1 and the login page Page 2. Using whatever server-side language you have available, you code a cookie on Page 2. This cookie will detect whether the user has gone to Page 1 before accessing Page 2. If not, then the cookie will send the user back to Page 1. If the user has gone to Page 1 before accessing Page 2, then the cookie lets the user through to the login page).

It still doesn't prevent someone from bookmarking the login page however But it's the best way around it, and it's not hard to do it using a server side language.

If you do go ahead, I suggest going over the Server Side Scripting forum and ask for pointers as to how to do so. It shouldn't be hard - good luck!