>>> 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 hi
On Sep 6, 1:32 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Sat, Sep 6, 2008 at 8:20 AM, Tim Chase <[EMAIL PROTECTED]>wrote:
>
> > Or one might be behind a load-balancing
> > NAT (I believe AOL did/does something like this) so requests from
> > the same user behind the NAT can appear to be
On Sat, Sep 6, 2008 at 8:20 AM, Tim Chase <[EMAIL PROTECTED]>wrote:
> Or one might be behind a load-balancing
> 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
> The question is this: what does Django do when multiple
> requests come in from different IP addresses that are
> reporting the same session id? Does Django dump the session
> data and create new session ids for the offending clients?
I believe the answer is "Django does the right thing", i.e.
Hi,
I have a question about Django's built-in session support. I've looked
around in the documentation (and the free Django on-line book) but
couldn't find an answer. Its the sort of question that could be
answered by a look through the code, but I'm new to Python and at the
moment just trying to
5 matches
Mail list logo