Hi,
We have been using something like this for ~2 years.
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 128bit
ID). Then applying an increment, with future requests having a higher id.
Perhaps that would
Same here, in our environment we:
* get current request id from a header
* validate it against our guidelines
* if not already present or does not pass validation:
* re-generate using `RAND_bytes()`
* propagate it to the upstream
* echo it back to the downstream
* log it to the access.log
It wou
Hello,
We are using such variable for more than a year, and I suggest to add
ability to extract request_id from header. It's very usefull for systems
with frontend and backend installed on different servers.
On Tue, Apr 26, 2016 at 7:38 PM, Vladimir Homutov wrote:
> details: http://hg.nginx.o
details: http://hg.nginx.org/nginx/rev/59f8f2dd8b31
branches:
changeset: 6531:59f8f2dd8b31
user: Vladimir Homutov
date: Tue Apr 26 19:31:46 2016 +0300
description:
Variable $request_id.
The variable contains text representation based on random data, usable as
a unique request identi
details: http://hg.nginx.org/nginx/rev/1d0e03db9f8e
branches:
changeset: 6530:1d0e03db9f8e
user: Roman Arutyunyan
date: Fri Dec 18 19:05:27 2015 +0300
description:
Upstream: the "transparent" parameter of proxy_bind and friends.
This parameter lets binding the proxy connection to a
details: http://hg.nginx.org/nginx/rev/cb8177ca0990
branches:
changeset: 6529:cb8177ca0990
user: Roman Arutyunyan
date: Wed Apr 13 15:42:47 2016 +0300
description:
Stream: prepared proxy_bind to accept parameters.
diffstat:
src/stream/ngx_stream_proxy_module.c | 57 ++
details: http://hg.nginx.org/nginx/rev/88f012eee7d8
branches:
changeset: 6528:88f012eee7d8
user: Roman Arutyunyan
date: Wed Apr 13 15:42:46 2016 +0300
description:
Upstream: prepared proxy_bind to accept parameters.
In addition, errors occurred while setting bind address are no long
details: http://hg.nginx.org/nginx/rev/be44757637dd
branches:
changeset: 6526:be44757637dd
user: Ruslan Ermilov
date: Tue Apr 26 18:26:18 2016 +0300
description:
Version bump.
diffstat:
src/core/nginx.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diffs (14 lines):
details: http://hg.nginx.org/nginx/rev/6d3a60a909c8
branches:
changeset: 6527:6d3a60a909c8
user: Ruslan Ermilov
date: Tue Apr 26 18:26:43 2016 +0300
description:
Removed some bitrot.
Removed NGX_CONF_MULTI unused since 1.3.4.
Removed ngx_url_t.one_addr unused since 1.3.10.
diffstat
details: http://hg.nginx.org/nginx/rev/9fc87d93c4ed
branches: stable-1.10
changeset: 6523:9fc87d93c4ed
user: Maxim Dounin
date: Tue Apr 26 16:30:30 2016 +0300
description:
Stable branch.
diffstat:
src/core/nginx.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diffs (
details: http://hg.nginx.org/nginx/rev/d4b7edd7fa81
branches: stable-1.10
changeset: 6524:d4b7edd7fa81
user: Maxim Dounin
date: Tue Apr 26 16:31:18 2016 +0300
description:
nginx-1.10.0-RELEASE
diffstat:
docs/xml/nginx/changes.xml | 14 ++
1 files changed, 14 insertions
details: http://hg.nginx.org/nginx/rev/efbdc2f66901
branches: stable-1.10
changeset: 6525:efbdc2f66901
user: Maxim Dounin
date: Tue Apr 26 16:31:18 2016 +0300
description:
release-1.10.0 tag
diffstat:
.hgtags | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diffs (8 lines)
Hello!
On Tue, Apr 26, 2016 at 05:07:19PM +0530, Pankaj Chaudhary wrote:
> Hi,
>
> I have requirement to create own cookie based on input and wirte the that
> cookie in header.
> whenever i need that i can read from header and use it.
>
>
> for example:-
>
> I have created my own cookie "th
Hi,
I have requirement to create own cookie based on input and wirte the that
cookie in header.
whenever i need that i can read from header and use it.
for example:-
I have created my own cookie "thissomevalue" worte in header and later the
same read from header.
Please check my code and let
14 matches
Mail list logo