Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71567 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91816 invoked from network); 25 Jan 2014 20:21:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jan 2014 20:21:18 -0000 Authentication-Results: pb1.pair.com header.from=bof@bof.de; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=bof@bof.de; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain bof.de designates 80.242.145.70 as permitted sender) X-PHP-List-Original-Sender: bof@bof.de X-Host-Fingerprint: 80.242.145.70 mars.intermailgate.com Received: from [80.242.145.70] ([80.242.145.70:40234] helo=mars.intermailgate.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 04/21-19300-BBC14E25 for ; Sat, 25 Jan 2014 15:21:17 -0500 Received: (qmail 2779 invoked by uid 1009); 25 Jan 2014 21:21:11 +0100 Received: from 209.85.216.173 by mars (envelope-from , uid 89) with qmail-scanner-1.25-st-qms (clamdscan: 0.96.2/18393. spamassassin: 3.3.1. perlscan: 1.25-st-qms. Clear:RC:1(209.85.216.173):. Processed in 0.067837 secs); 25 Jan 2014 20:21:11 -0000 X-Antivirus-MYDOMAIN-Mail-From: bof@bof.de via mars X-Antivirus-MYDOMAIN: 1.25-st-qms (Clear:RC:1(209.85.216.173):. Processed in 0.067837 secs Process 2765) Received: from mail-qc0-f173.google.com (gmail@bof.de@209.85.216.173) by mars.intermailgate.com with RC4-SHA encrypted SMTP; 25 Jan 2014 21:21:11 +0100 Received: by mail-qc0-f173.google.com with SMTP id i8so6114575qcq.18 for ; Sat, 25 Jan 2014 12:21:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eZeaKP+TNVELkbWsTjEFTA2bICFUDUfSKvc0IsqGbAY=; b=Ut9spxQkAbvTYSeA9lm/qDx38yDb+LusuKgroeZEhRWdMCVCstz7B4VgZ5tOu1H9jc 9EKouxGpV0LKbaFuTEo2qzYn5wWBLyAX13nemNyJfXDMVv5rx66oUyK9lBfHN3MdR6kN Kdw4x5jC5b5s1ToIYfsmrGq+5LVqO8SeHI4jpnl9ZoZcXsv7hpiJyHfsNBlL70vZ2akY K5W7K1mhKstGxi3lesaeSp4C7TWvW6sJj7UmVvoIDxrAeI0sqfATDFhsGV6M/UJLY3K6 38nKkYzhY2uG8TJp9TCOLi6cC18qKOA4jlxaWc55o8wrOYk4MYOmGZHYQayEY3XpEJTc +wbw== MIME-Version: 1.0 X-Received: by 10.224.167.84 with SMTP id p20mr31205873qay.24.1390681269791; Sat, 25 Jan 2014 12:21:09 -0800 (PST) Received: by 10.140.94.75 with HTTP; Sat, 25 Jan 2014 12:21:09 -0800 (PST) Received: by 10.140.94.75 with HTTP; Sat, 25 Jan 2014 12:21:09 -0800 (PST) In-Reply-To: References: <52E31FB6.9010408@ajf.me> <52E3C606.6000301@heigl.org> Date: Sat, 25 Jan 2014 21:21:09 +0100 Message-ID: To: Andrey Andreev Cc: internals Content-Type: multipart/alternative; boundary=089e0153747e14f1c604f0d137db Subject: Re: [PHP-DEV] Session IP address matching From: bof@bof.de (Patrick Schaaf) --089e0153747e14f1c604f0d137db Content-Type: text/plain; charset=ISO-8859-1 Am 25.01.2014 17:30 schrieb "Andrey Andreev" : > > Also, "not fixed" doesn't necessarily mean changing addresses on every > few minutes For some users it means changing addresses at every request. The traditional thing was the AOL Proxy. I regularly see the same for mobile provider users from places like Singapore, and for mobile Opera browser users that run through "optimizing" proxies run by Opera. With the current Google Chrome update such a "feature" arrives in google world, so over the next year it will become even more common place - probably making geoIP also a thing of the glorious past... So, unless you know your userbase exactly and know exactly that they will not be affected by such issues, fixing the session to the client IP just doesn't fly. best regards Patrick --089e0153747e14f1c604f0d137db--