>>> NAT (I believe AOL did/does something like this) so requests from >>> the same user behind the NAT can appear to be coming from >>> different public IP addresses. >> >> AOL certainly does this. Either that or my own little web site has an >> astonishingly high number of different AOL users hitting it. > > I wonder - what percentage of net users do use AOL as their ISP?
A disappointingly large number...I think my grandparents still use it for dial-up despite efforts to get them moved to something less wallet-emptying. > So, I think I won't bother with the IP address checking. A fairly good idea...the only time I've found that IP address checking was worthwhile was on an intranet rather than the public internet, so there were known IP-address allocations. An intranet app doesn't necessarily predicate IP checking, as you might still have address hand-offs as a user unplugs from the wired LAN and moves to a WiFi subnet. So it should be the known network architecture combined with a legitimate business-rule need (that accommodates the architecture) that predicates any sort of IP address checking. This is sufficiently rare that you most likely don't want/need to invest the time in doing so. -tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
