Realip: fixed uninitialized memory access.
Previously, the realip module could be left with uninitialized context after an error in the ngx_http_realip_set_addr() function. That context could be later accessed by $realip_remote_addr and $realip_remote_port variable handlers.
This commit is contained in:
parent
2d024ed616
commit
9c0040b43c
1 changed files with 1 additions and 1 deletions
|
@ -264,7 +264,6 @@ ngx_http_realip_set_addr(ngx_http_request_t *r, ngx_addr_t *addr)
|
|||
}
|
||||
|
||||
ctx = cln->data;
|
||||
ngx_http_set_ctx(r, ctx, ngx_http_realip_module);
|
||||
|
||||
c = r->connection;
|
||||
|
||||
|
@ -282,6 +281,7 @@ ngx_http_realip_set_addr(ngx_http_request_t *r, ngx_addr_t *addr)
|
|||
ngx_memcpy(p, text, len);
|
||||
|
||||
cln->handler = ngx_http_realip_cleanup;
|
||||
ngx_http_set_ctx(r, ctx, ngx_http_realip_module);
|
||||
|
||||
ctx->connection = c;
|
||||
ctx->sockaddr = c->sockaddr;
|
||||
|
|
Loading…
Reference in a new issue