On Wed, Jun 10, 2009 at 11:53 PM, merlin corey
That is precisely the kind of control required to take place in an
upstream application, not nginx. Nginx should be thought of as sort
of a signal processor, that is, it sits in a stream and does its
business as quickly and efficiently as possible. Waiting on databases
is neither quick nor efficient.
First of all thanks for your answer Merlin!
I think it as an option so user have the choice using it or not. And in
way user decides to put load on server or not. But in short there is no
Also there is nothing secure about cookies, which can be completely
manipulated by the client. Session data, on the other hand, is
internal and therefore much more reliable (and is basically what you
want to use).
I know it but not as easy as cheating on referrer. I do not look for
the perfect protection system actually but good enough for basic
and using as much of different techniques as possible but not more. And
not want to write any external code (PHP in my case) let’s say I am
I am able to store and retrieve used cookies and their deadline within
the system would be pretty useful.
Is nginx have session data or some external processing required?