On Sun, Nov 29, 2009 at 6:56 PM, Nick Arnett <nick.arn...@gmail.com> wrote:
> > > On Sun, Nov 29, 2009 at 2:24 PM, The New Hanoian <newhano...@gmail.com>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 missing something? > > > Um, yes. You're missing the fact that you already have it, since you are > the one who configures Django's port. The client can only contact you on > the port it is running on, of course. > > In other words, the client port number always is the same as the server > port number. Gotta be so. > > 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 numbers each system uses are up to that system. Obviously you want the server to listen on a "well-known" port most of the time, though as you have observed the Django administrator can configure the server to listen on any desired port. But the client really doesn't care - it just expects the server to reply to the same port number it sent its request from. regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
