#
2133:46433e3cef45 |
| 20-Jun-2022 |
Zhidao HONG |
Router: forwared header replacement.
|
Revision tags: 1.27.0-1, 1.27.0 |
|
#
2078:0996dd223cdd |
| 18-Dec-2021 |
Alejandro Colomar |
Fixed indentation.
Some lines (incorrectly) had an indentation of 3 or 5, or 7 or 9, or 11 or 13, or 15 or 17 spaces instead of 4, 8, 12, or 16. Fix them.
Found with:
$ find src -type f | xargs g
Fixed indentation.
Some lines (incorrectly) had an indentation of 3 or 5, or 7 or 9, or 11 or 13, or 15 or 17 spaces instead of 4, 8, 12, or 16. Fix them.
Found with:
$ find src -type f | xargs grep -n '^ [^ ]'; $ find src -type f | xargs grep -n '^ [^ *]'; $ find src -type f | xargs grep -n '^ [^ ]'; $ find src -type f | xargs grep -n '^ [^ *]'; $ find src -type f | xargs grep -n '^ [^ +]'; $ find src -type f | xargs grep -n '^ [^ *+]'; $ find src -type f | xargs grep -n '^ [^ +]'; $ find src -type f | xargs grep -n '^ [^ *+]';
show more ...
|
Revision tags: 1.26.1-1, 1.26.1, 1.26.0-1, 1.26.0 |
|
#
2002:c802cd567711 |
| 11-Nov-2021 |
Valentin Bartenev |
Removed the execute permission bit from "nxt_h1proto.c".
It was accidentally added in 4645a43bc248.
|
Revision tags: 1.25.0-1, 1.25.0 |
|
#
1927:ac8d11e34427 |
| 03-Aug-2021 |
Max Romanov |
Fixed dead assignments.
Found by Clang Static Analyzer.
|
Revision tags: 1.24.0-1, 1.24.0 |
|
#
1884:4645a43bc248 |
| 26-May-2021 |
Andrey Suvorov |
Fixing crash during TLS connection shutdown.
A crash was caused by an incorrect timer handler nxt_h1p_idle_timeout() if SSL_shutdown() returned SSL_ERROR_WANT_READ/SSL_ERROR_WANT_WRITE.
The flag SS
Fixing crash during TLS connection shutdown.
A crash was caused by an incorrect timer handler nxt_h1p_idle_timeout() if SSL_shutdown() returned SSL_ERROR_WANT_READ/SSL_ERROR_WANT_WRITE.
The flag SSL_RECEIVED_SHUTDOWN is used to avoid getting SSL_ERROR_WANT_READ, so the server won't wait for a close notification from a client.
For SSL_ERROR_WANT_WRITE, a correct timer handler is set up.
show more ...
|
Revision tags: 1.23.0-1, 1.23.0, 1.22.0-1, 1.22.0 |
|
#
1733:dab8544b5440 |
| 07-Dec-2020 |
Valentin Bartenev |
PHP: populating PHP_AUTH_* server variables.
This closes #498 issue on GitHub.
|
#
1732:61c7915b5b6a |
| 07-Dec-2020 |
Valentin Bartenev |
HTTP: fixed status line format for unknown status codes.
According to Section #3.1.2 of RFC 7230, after the status code there must be a space even if the reason phrase is empty.
Also, only 3 digits
HTTP: fixed status line format for unknown status codes.
According to Section #3.1.2 of RFC 7230, after the status code there must be a space even if the reason phrase is empty.
Also, only 3 digits allowed.
This closes #507 issue on GitHub.
show more ...
|
Revision tags: 1.21.0-1, 1.21.0 |
|
#
1709:1fe93c17d23f |
| 17-Nov-2020 |
Valentin Bartenev |
HTTP parser: allowed more characters in header field names.
Previously, all requests that contained in header field names characters other than alphanumeric, or "-", or "_" were rejected with a 400
HTTP parser: allowed more characters in header field names.
Previously, all requests that contained in header field names characters other than alphanumeric, or "-", or "_" were rejected with a 400 "Bad Request" error response.
Now, the parser allows the same set of characters as specified in RFC 7230, including: "!", "#", "$", "%", "&", "'", "*", "+", ".", "^", "`", "|", and "~". Header field names that contain only these characters are considered valid.
Also, there's a new option introduced: "discard_unsafe_fields". It accepts boolean value and it is set to "true" by default.
When this option is "true", all header field names that contain characters in valid range, but other than alphanumeric or "-" are skipped during parsing. When the option is "false", these header fields aren't skipped.
Requests with non-valid characters in header field names according to RFC 7230 are rejected regardless of "discard_unsafe_fields" setting.
This closes #422 issue on GitHub.
show more ...
|
Revision tags: 1.20.0-1, 1.20.0 |
|
#
1619:6d08a02c7300 |
| 30-Sep-2020 |
Max Romanov |
Fixing router connection pool leakage.
The connection's local socket address is allocated from the connection pool before the request is passed to the application; however, with keep-alive connectio
Fixing router connection pool leakage.
The connection's local socket address is allocated from the connection pool before the request is passed to the application; however, with keep-alive connections, this field was unconditionally reset by a socket configuration value that could be NULL. For the next request, the address was allocated again from the same connection pool. Nonetheless, all leaked addresses were released when the connection was closed.
The issue introduced in changeset 5c7dd85fabd5.
show more ...
|
#
1614:ecbc08abe2cc |
| 29-Sep-2020 |
Max Romanov |
Supporting HTTP/1.0 keep-alive.
The Apache HTTP server benchmarking tool, ab, issues HTTP/1.0 requests with the 'Connection: Keep-Alive' header and expects a 'Connection: Keep-Alive' header in the r
Supporting HTTP/1.0 keep-alive.
The Apache HTTP server benchmarking tool, ab, issues HTTP/1.0 requests with the 'Connection: Keep-Alive' header and expects a 'Connection: Keep-Alive' header in the response.
show more ...
|
#
1600:98d5a4af7282 |
| 18-Sep-2020 |
Igor Sysoev |
Fixed segmentation fault during reconfiguration.
If idle connection was closed before h1proto had been allocated then c->socket.data is NULL. This happens if nxt_h1p_idle_response() is called by nx
Fixed segmentation fault during reconfiguration.
If idle connection was closed before h1proto had been allocated then c->socket.data is NULL. This happens if nxt_h1p_idle_response() is called by nxt_h1p_idle_close(). However, h1p->conn_write_tail is used only in nxt_h1p_request_send() that would not be called after nxt_h1p_idle_response().
The bug was introduced in f237e8c553fd.
show more ...
|
#
1599:28e8fd9ad657 |
| 18-Sep-2020 |
Igor Sysoev |
Fixed segmentation fault during reconfiguration.
|
#
1598:f060f13fe540 |
| 18-Sep-2020 |
Igor Sysoev |
Fixed use-after-free error during reconfiguration.
An idle connection was not removed from idle connection list if the connections detected that listening socket had been closed.
|
Revision tags: 1.19.0-1, 1.19.0 |
|
#
1534:dd6867b3a02e |
| 05-Aug-2020 |
Valentin Bartenev |
Improved mkstemp() error reporting.
The invocation parameters should be logged as well, notably the path of the file that is failed to be created.
Also, log level changed to ALERT as it's quite cri
Improved mkstemp() error reporting.
The invocation parameters should be logged as well, notably the path of the file that is failed to be created.
Also, log level changed to ALERT as it's quite critical error.
show more ...
|
#
1505:d18f2b38596b |
| 23-Jun-2020 |
Igor Sysoev |
Upstream chunked transfer encoding support.
|
Revision tags: 1.18.0-1, 1.18.0, 1.17.0-1, 1.17.0 |
|
#
1459:358b957ca294 |
| 16-Apr-2020 |
Max Romanov |
Using malloc/free for the http fields hash.
This is required due to lack of a graceful shutdown: there is a small gap between the runtime's memory pool release and router process's exit. Thus, a wor
Using malloc/free for the http fields hash.
This is required due to lack of a graceful shutdown: there is a small gap between the runtime's memory pool release and router process's exit. Thus, a worker thread may start processing a request between these two operations, which may result in an http fields hash access and subsequent crash.
To simplify issue reproduction, it makes sense to add a 2 sec sleep before exit() in nxt_runtime_exit().
show more ...
|
#
1457:af93c866b4f0 |
| 15-Apr-2020 |
Igor Sysoev |
Fixed crash that occurs when idle connections are closed forcibly.
|
#
1432:f650ced3012a |
| 20-Mar-2020 |
Valentin Bartenev |
Implemented "location" option for "return" action.
This allows to specify redirects:
{ "action": { "return": 301, "location": "https://www.example.com/" } }
|
#
1418:073c9c008b83 |
| 19-Mar-2020 |
Max Romanov |
Completing buffers immediately
This fixes crash introduced in 039b00e32e3d.
|
#
1417:039b00e32e3d |
| 19-Mar-2020 |
Max Romanov |
Completing request header buffers to avoid memory leak.
Before this fix, only persistent connection request buffers were completed.
This issue was introduced in dc403927ab0b.
|
Revision tags: 1.16.0-1, 1.16.0 |
|
#
1403:1cee885b7f10 |
| 12-Mar-2020 |
Max Romanov |
Using disk file to store large request body.
This closes #386 on GitHub.
|
#
1401:c88f739aac1c |
| 12-Mar-2020 |
Max Romanov |
Checking Content-Length value right after header parse.
The check was moved from the request body read stage.
|
#
1394:20b41ebfff79 |
| 06-Mar-2020 |
Igor Sysoev |
Round robin upstream added.
|
Revision tags: 1.15.0-1, 1.15.0, 1.14.0-1, 1.14.0 |
|
#
1318:f237e8c553fd |
| 24-Dec-2019 |
Max Romanov |
Introducing write tail reference to avoid buffer chain iteration.
|
Revision tags: 1.13.0-1, 1.13.0 |
|
#
1271:d9c8ee25590a |
| 14-Nov-2019 |
Igor Sysoev |
Processing inconsistent proxied response length.
Keepalive connection is disabled if upstream response length differs from specified in the "Content-Length" field value.
|