On Mon, 2004-01-26 at 20:17, b c r wrote: > so here's what i want. i want to just block one ip, or possibly 1 subnet. > I want to block one user from viewing my web pages, and i think she either > uses dial up or has a dynamic ip. Anyway, here's what I want. > > instead of just denying it at the apache level, i'd like for javascript to > look at the ip, and then if it matches send it to another webpage that > says i'm sorry but you dont have access. cold? maybe, but less cold than > a strait up 404.
I'm not even going to investigate if it's possible. Instead, in the great tradition of all lists, I'm going to tell you that what you want to do is foolish. Never trust the client for anything. Policy should be enforced on the server side; client-side scripting is only a convenience. It is very easy to work around. You're obviously not trying to stop an out-of-control bot from sucking up bandwidth, or something like that. Sounds like you're dealing with a malicious or annoying user. Asking their browser to "pretty place with sugar on top" lock them out is probably not a plan for success. BTW, yes that's a new URL in my sig. So, uh, I guess this is the official launch or something. -- Stuart Jansen <[EMAIL PROTECTED] http://buscaluz.org/ AIM:StuartMJansen> When in doubt, use brute force. -- Ken Thompson, co-creator of Unix
signature.asc
Description: This is a digitally signed message part
____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
