nginx.git/src/http/ngx_http_special_response.c, branch release-1.28.2 nginx All known output headers can be linked lists now. 2022-05-30T18:25:45+00:00 Maxim Dounin mdounin@mdounin.ru 2022-05-30T18:25:45+00:00 e59c2096ae9d561997ad2d64d61094503e6be4c3 The h->next pointer properly provided as NULL in all cases where known output headers are added. Note that there are 3rd party modules which might not do this, and it might be risky to rely on this for arbitrary headers. 
The h->next pointer properly provided as NULL in all cases where known
output headers are added.

Note that there are 3rd party modules which might not do this, and it
might be risky to rely on this for arbitrary headers.
Clean up trailers in ngx_http_clean_header() as well. 2021-01-26T09:39:28+00:00 Sergey Kandaurov pluknet@nginx.com 2021-01-26T09:39:28+00:00 56f53316837271a8cbb1d99f638e28d268a00d45 The function has not been updated with introduction of trailers support in 7034:1b068a4e82d8 (1.13.2). 
The function has not been updated with introduction of trailers support
in 7034:1b068a4e82d8 (1.13.2).
Discard request body when redirecting to a URL via error_page. 2019-12-23T12:45:46+00:00 Ruslan Ermilov ru@nginx.com 2019-12-23T12:45:46+00:00 c1be55f97211d38b69ac0c2027e6812ab8b1b94e Reported by Bert JW Regeer and Francisco Oca Gonzalez. 
Reported by Bert JW Regeer and Francisco Oca Gonzalez.
Removed bgcolor attribute on body in error pages and autoindex. 2018-09-19T14:26:47+00:00 Nova DasSarma nova@novalinium.com 2018-09-19T14:26:47+00:00 8117b3f5a06b68afb292ddd19bf6ee6000707232 The bgcolor attribute overrides compatibility settings in browsers and leads to undesirable behavior when the default font color is set to white in the browser, since font-color is not also overridden. 
The bgcolor attribute overrides compatibility settings in browsers
and leads to undesirable behavior when the default font color is set
to white in the browser, since font-color is not also overridden.
Don't pretend we support HTTP major versions >1 as HTTP/1.1. 2017-04-25T20:39:13+00:00 Ruslan Ermilov ru@nginx.com 2017-04-25T20:39:13+00:00 8ae2bc932013b838b925cdbb0cae59f743e699c7 






Added support for the "308 Permanent Redirect" (ticket #877).
2017-04-11T01:13:46+00:00

Simon Leblanc
contact@leblanc-simon.eu

2017-04-11T01:13:46+00:00

8ee2de5e9c930273c99a03452e7336f8a393ec42












Added support for "429 Too Many Requests" response (RFC6585).
2017-03-24T09:48:03+00:00

Piotr Sikora
piotrsikora@google.com

2017-03-24T09:48:03+00:00

c3ce606652aeac465895ab8eb8c6fc195d7db16b

This change adds reason phrase in status line and pretty response body
when "429" status code is used in "return", "limit_conn_status" and/or
"limit_req_status" directives.

Signed-off-by: Piotr Sikora <piotrsikora@google.com>





This change adds reason phrase in status line and pretty response body
when "429" status code is used in "return", "limit_conn_status" and/or
"limit_req_status" directives.

Signed-off-by: Piotr Sikora <piotrsikora@google.com>







Implemented the "server_tokens build" option.
2017-01-31T09:09:40+00:00

Ruslan Ermilov
ru@nginx.com

2017-01-31T09:09:40+00:00

7e080678d61d946891c035d79b73715f1cc57682

Based on a patch by Tom Thorogood.





Based on a patch by Tom Thorogood.







Style: switch.
2016-11-04T16:12:19+00:00

Ruslan Ermilov
ru@nginx.com

2016-11-04T16:12:19+00:00

8e9f1df637160ec20990601976e140b8d3cffc0b












Do not set last_buf flag in subrequests.
2016-10-03T17:48:51+00:00

Roman Arutyunyan
arut@nginx.com

2016-10-03T17:48:51+00:00

f3bbd1c87f0bc97367603c3254c1465d3c622d1f

The last_buf flag should only be set in the last buffer of the main request.
Otherwise, several last_buf flags can appear in output.  This can, for example,
break the chunked filter, which will include several final chunks in output.





The last_buf flag should only be set in the last buffer of the main request.
Otherwise, several last_buf flags can appear in output.  This can, for example,
break the chunked filter, which will include several final chunks in output.