[nginx] Variable $request_id.
albertcasademont at gmail.com
Wed Apr 27 14:42:28 UTC 2016
To be clear, that extension also uses a "request_id" variable, accepting
this patch would effectively break that extension, which I believe quite a
lof of people also use.
On Wed, Apr 27, 2016 at 5:40 PM, Albert Casademont <
albertcasademont at gmail.com> wrote:
> Hi all,
> We've been using this extension for quite a long time now, it's based on
> UUIDs and it works flawlessly, no need to reinvent the wheel here!
> On Wed, Apr 27, 2016 at 5:30 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:
>> On Wed, Apr 27, 2016 at 03:23:51PM +1000, SplitIce wrote:
>> > For ours we used a random number to start and the Process ID & Process
>> > start time to try and increase uniqueness between reloads (ours is a
>> > ID). Then applying an increment, with future requests having a higher
>> > Perhaps that would be better than just 128bit of random data?
>> Using process id & start time is believed to be particularly bad
>> approach in virtualized environments where multiple identical
>> virtual machines and/or containers can start at the same time.
>> Maxim Dounin
>> nginx-devel mailing list
>> nginx-devel at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx-devel