>You can run the web server on virtually any port without difficulty.
>Restricting port 80 just begins a shell game. The user puts it on port
>81, you restrict port 81, he puts it on 82. Etc.
Sure, if he figures it out. But you can also deny *everything* except for
the services you allow him to have. Then he has to play a real annoying
shell game at best, putting the web server on one of the ports you HAVE
allowed. Bottom line is that you have to decide whether to allow an open
system where the customer can do most anything within reason, or a
restricted system where you try to control his every move. If you are
silly enough to offer "unlimited", "flat rate", "unmetered" access or
whatever the current euphemism is, then you should not be surprised when
others try to take advantage of that and NOT pay your dedicated web rates
and set up their own server on their "unlimited" account. Then you spend
most of your time trying to figure out how to deny your user now that you
let the cat out of the bag so to speak. Doesn't matter what you gave the
customer when you signed them up for marketing reasons. You then spend
the time figuring out whether they are defeating your timeouts, running
servers, doing multiple logins, etc. when you could be charging them
realistic rates based on what they are costing you.