Mercurial > hg > nginx-quic
view docs/dtd/change_log_conf.dtd @ 6909:5850fed24639
Upstream: read handler cleared on upstream finalization.
With "proxy_ignore_client_abort off" (the default), upstream module changes
r->read_event_handler to ngx_http_upstream_rd_check_broken_connection().
If the handler is not cleared during upstream finalization, it can be
triggered later, causing unexpected effects, if, for example, a request
was redirected to a different location using error_page or X-Accel-Redirect.
In particular, it makes "proxy_ignore_client_abort on" non-working after
a redirection in a configuration like this:
location = / {
error_page 502 = /error;
proxy_pass http://127.0.0.1:8082;
}
location /error {
proxy_pass http://127.0.0.1:8083;
proxy_ignore_client_abort on;
}
It is also known to cause segmentation faults with aio used, see
http://mailman.nginx.org/pipermail/nginx-ru/2015-August/056570.html.
Fix is to explicitly set r->read_event_handler to ngx_http_block_reading()
during upstream finalization, similar to how it is done in the request body
reading code and in the limit_req module.
author | Maxim Dounin <mdounin@mdounin.ru> |
---|---|
date | Fri, 10 Feb 2017 20:24:26 +0300 |
parents | 551102312e19 |
children |
line wrap: on
line source
<!ELEMENT configuration (length, start, indent, changes+) > <!ELEMENT length (#PCDATA) > <!ELEMENT start (#PCDATA) > <!ELEMENT indent (#PCDATA) > <!ELEMENT changes (title, length, bugfix, feature, change, workaround, (month, month, month, month, month, month, month, month, month, month, month, month)?) > <!ATTLIST changes lang ( ru | en) #REQUIRED> <!ELEMENT title (#PCDATA) > <!ELEMENT bugfix (#PCDATA) > <!ELEMENT feature (#PCDATA) > <!ELEMENT change (#PCDATA) > <!ELEMENT workaround (#PCDATA) > <!ELEMENT month (#PCDATA) >