On Sun, Nov 29, 2009 at 8:33 PM, Nick Arnett wrote:
> On Sun, Nov 29, 2009 at 4:01 PM, Steve Holden wrote:
>
>
>>
>>> Not at all. The client will typically use an "ephemeral" port (one it
>> obtains by saying to its local TCP layer "gimme a port number, I don't care
>> what it is"). The connect
On Sun, Nov 29, 2009 at 4:01 PM, Steve Holden wrote:
>
>
>> Not at all. The client will typically use an "ephemeral" port (one it
> obtains by saying to its local TCP layer "gimme a port number, I don't care
> what it is"). The connection (any connection) has *two* endpoints, and the
> port numb
On Sun, Nov 29, 2009 at 6:56 PM, Nick Arnett wrote:
>
>
> On Sun, Nov 29, 2009 at 2:24 PM, The New Hanoian wrote:
>
>> Hi,
>>
>> I'm learning Django. In the tutorial i find that the client IP address
>> can be retrieve through HttpRequest.META["REMOTE_ADDR"]. But I
>> couldn't find a way to retri
On Sun, Nov 29, 2009 at 2:24 PM, The New Hanoian wrote:
> Hi,
>
> I'm learning Django. In the tutorial i find that the client IP address
> can be retrieve through HttpRequest.META["REMOTE_ADDR"]. But I
> couldn't find a way to retrieve the client port number. I think it
> should be obvious. Am I m
4 matches
Mail list logo