Ron Goral wrote: > ... > I can figure a way to react to a changed IP, but my curiosity runs > more toward why this AOL browser is switching IPs during a session. > I could understand if the user were to disconnect then reconnect his > internet, but this is just a change of web pages basically. Perhaps > this is just another reason to avoid using AOL, but I'd like to > discover a reason for this seemingly arbitrary behavior.
I don't really know the answer, but HTTP is not a session-oriented protocol. Each request is independent of all other requests (HTTP 1.1 allows reusing connections to a certain extent, but not for the purposes of maintaining a session). Between a change of pages, the TCP connection is torn down and built back up, so the IP is subject to change. AOL may be using a pool of proxies and handing his requests off to different proxies in a load-balancing scheme. The point is, you can't reliably use REMOTE_ADDR for session management. You've got to pass some kind of data back and forth in the request and response themselves. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
