aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Fix for connection drops with AIO.Maxim Dounin2011-10-11
| | | | | Connections serving content with AIO to fast clients were dropped with "client timed out" messages after send_timeout from response start.
* Autoindex: escape html in file names.Maxim Dounin2011-10-11
|
* Autoindex: escape '?' in file names.Maxim Dounin2011-10-11
| | | | | | | | | | | | | | | | For files with '?' in their names autoindex generated links with '?' not escaped. This resulted in effectively truncated links as '?' indicates query string start. This is an updated version of the patch originally posted at [1]. It introduces generic NGX_ESCAPE_URI_COMPONENT which escapes everything but unreserved characters as per RFC 3986. This approach also renders unneeded special colon processing (as colon is percent-encoded now), it's dropped accordingly. [1] http://nginx.org/pipermail/nginx-devel/2010-February/000112.html Reported by Konstantin Leonov.
* Improved access log escaping to better protect other software.Maxim Dounin2011-10-11
| | | | | | | Some character sets (notably ISO-8859-1) have C1 control characters in upper half, make sure to escape them. Reported by Jesus Olmos Gonzalez.
* Fixing directive name in error message if types hash size is not enough.Igor Sysoev2011-10-11
|
* Fixing mp4 module seeking on 32-bit platforms.Igor Sysoev2011-10-11
|
* Fixed macro name.Ruslan Ermilov2011-10-10
|
* Releasing memory of idle SSL connection. This saves about 34K per SSLIgor Sysoev2011-10-07
| | | | | connection. The SSL_MODE_RELEASE_BUFFERS option is available since OpenSSL 1.0.0d.
* Disabling SSL compression. This saves about 300K per SSL connection.Igor Sysoev2011-10-07
| | | | The SSL_OP_NO_COMPRESSION option is available since OpenSSL 1.0.0.
* Version bump.Igor Sysoev2011-10-07
|
* Improved ngx_parse_time() code readability.Ruslan Ermilov2011-10-07
|
* Tweaked error messages.Ruslan Ermilov2011-10-07
|
* Version bump.Igor Sysoev2011-10-05
|
* Fixed cache bypass caching of non-cacheable replies (ticket #21).Maxim Dounin2011-10-05
| | | | | | | | If cache was bypassed with proxy_cache_bypass, cache-controlling headers (Cache-Control, Expires) wasn't considered and response was cached even if it was actually non-cacheable. Patch by John Ferlito.
* Added uwsgi_buffering and scgi_buffering directives.Maxim Dounin2011-09-30
| | | | Patch by Peter Smit.
* Using strtod() instead of atofp() to support a lot of digits after dot inIgor Sysoev2011-09-30
| | | | "start" parameter value.
* Fix of building on platforms with 32-bit off_t. (closed #23)Igor Sysoev2011-09-29
|
* Fixed segmentation fault with empty config on Windows.Maxim Dounin2011-09-27
| | | | | See here for report: http://mailman.nginx.org/pipermail/nginx-ru/2011-September/043288.html
* Fix for "ssl_session_cache builtin" (broken since 1.1.1, r3993).Maxim Dounin2011-09-27
|
* Better handling of late upstream creation.Maxim Dounin2011-09-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Configuration with duplicate upstream blocks defined after first use, i.e. like server { ... location / { proxy_pass http://backend; } } upstream backend { ... } upstream backend { ... } now correctly results in "duplicate upstream" error. Additionally, upstream blocks defined after first use now handle various server directive parameters ("weight", "max_fails", etc.). Previously configuration like server { ... location / { proxy_pass http://backend; } } upstream backend { server 127.0.0.1 max_fails=5; } incorrectly resulted in "invalid parameter "max_fails=5"" error.
* Cache: fix for sending of stale responses.Maxim Dounin2011-09-27
| | | | | | | | | | | | | | | For normal cached responses ngx_http_cache_send() sends last buffer and then request finalized via ngx_http_finalize_request() call, i.e. everything is ok. But for stale responses (i.e. when upstream died, but we have something in cache) the same ngx_http_cache_send() sends last buffer, but then in ngx_http_upstream_finalize_request() another last buffer is send. This causes duplicate final chunk to appear if chunked encoding is used (and resulting problems with keepalive connections and so on). Fix this by not sending in ngx_http_upstream_finalize_request() another last buffer if we know response was from cache.
* Cache: fix for sending of empty responses.Maxim Dounin2011-09-27
| | | | | Revert wrong fix for empty responses introduced in 0.8.31 and apply new one, rewritten to match things done by static module as close as possible.
* Incorrect special case for "return 204" removed.Maxim Dounin2011-09-27
| | | | | | | | | | | | | | | | | | | | | | | | | The special case in question leads to replies without body in configuration like location / { error_page 404 /zero; return 404; } location /zero { return 204; } while replies with empty body are expected per protocol specs. Correct one will look like if (status == NGX_HTTP_NO_CONTENT) { rc = ngx_http_send_header(r); if (rc == NGX_ERROR || r->header_only) { return rc; } return ngx_http_send_special(r, NGX_HTTP_LAST); } though it looks like it's better to drop this special case at all.
* Fix for "return 202" not discarding body.Maxim Dounin2011-09-27
| | | | | | | | | | | | | | | | | | | Big POST (not fully preread) to a location / { return 202; } resulted in incorrect behaviour due to "return" code path not calling ngx_http_discard_request_body(). The same applies to all "return" used with 2xx/3xx codes except 201 and 204, and to all "return ... text" uses. Fix is to add ngx_http_discard_request_body() call to ngx_http_send_response() function where it looks appropriate. Discard body call from emtpy gif module removed as it's now redundant. Reported by Pyry Hakulinen, see http://mailman.nginx.org/pipermail/nginx/2011-August/028503.html
* Fix for double content when return is used in error_page handler.Maxim Dounin2011-09-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Test case: location / { error_page 405 /nope; return 405; } location /nope { return 200; } This is expected to return 405 with empty body, but in 0.8.42+ will return builtin 405 error page as well (though not counted in Content-Length, thus breaking protocol). Fix is to use status provided by rewrite script execution in case it's less than NGX_HTTP_BAD_REQUEST even if r->error_status set. This check is in line with one in ngx_http_script_return_code(). Note that this patch also changes behaviour for "return 302 ..." and "rewrite ... redirect" used as error handler. E.g. location / { error_page 405 /redirect; return 405; } location /redirect { rewrite ^ http://example.com/; } will actually return redirect to "http://example.com/" instead of builtin 405 error page with meaningless Location header. This looks like correct change and it's in line with what happens on e.g. directory redirects in error handlers.
* Fix for incorrect 201 replies from dav module.Maxim Dounin2011-09-27
| | | | | | | | | | | | | | | Replies with 201 code contain body, and we should clearly indicate it's empty if it's empty. Before 0.8.32 chunked was explicitly disabled for 201 replies and as a result empty body was indicated by connection close (not perfect, but worked). Since 0.8.32 chunked is enabled, and this causes incorrect responses from dav module when HTTP/1.1 is used: with "Transfer-Encoding: chunked" but no chunks at all. Fix is to actually return empty body in special response handler instead of abusing r->header_only flag. See here for initial report: http://mailman.nginx.org/pipermail/nginx-ru/2010-October/037535.html
* Proxy: logging levels tuned, double logging fixed.Maxim Dounin2011-09-25
|
* Proxy: whitespaces after chunk size allowed.Maxim Dounin2011-09-25
| | | | | Whitespaces after chunk size seems to be be allowed by the "implied *LWS" rule and emitted by some servers.
* Upstream: clearing of u->peer.connection on close.Maxim Dounin2011-09-25
| | | | | | This fixes crashes observed with some 3rd party balancer modules. Standard balancer modules (round-robin and ip hash) explicitly set pc->connection (aka u->peer.connection) to NULL and aren't affected.
* Fixed error message.Ruslan Ermilov2011-09-23
|
* Fix of separate pool for upstream connections (r4117).Maxim Dounin2011-09-20
| | | | | Pool may not be created if connection was created but rejected in connect() call. Make sure to check if it is here before trying to destroy it.
* Fixed loss of chain links in ngx_event_pipe_read_upstream().Maxim Dounin2011-09-20
|
* Fixed loss of chain links in fastcgi module.Maxim Dounin2011-09-20
|
* Fix of cpu hog in event pipe.Maxim Dounin2011-09-20
| | | | | | | | | | | | | If client closed connection in ngx_event_pipe_write_to_downstream(), buffers in the "out" chain were lost. This caused cpu hog if all available buffers were in the "out" chain. Fix is to call ngx_chain_update_chains() before checking return code of output filter to avoid loosing buffers in the "out" chain. Note that this situation (all available buffers in the "out" chain) isn't normal, it should be prevented by busy buffers limit. Though right now it may happen with complex protocols like fastcgi. This should be addressed separately.
* The "worker_aio_requests" directive.Igor Sysoev2011-09-20
| | | | | | | | | The default value is 32 AIO simultaneous requests per worker. Previously they were hardcoded to 1024, and it was too large, since Linux allocated them early on io_setup(), but not on request itself. So with default value of /proc/sys/fs/aio-max-nr equal to 65536 only 64 worker processes could be run simultaneously. 32 AIO requests are enough for modern disks even if server runs only 1 worker.
* Replaced "can not" with "cannot" and "could not" in a bunch of places.Ruslan Ermilov2011-09-19
| | | | Fixed nearby grammar errors.
* Cosmetics: replaced NGX_CONF_TAKE1 to NGX_CONF_FLAG for "sendfile"Ruslan Ermilov2011-09-19
| | | | | | and "chunked_transfer_encoding" directives, to be in line with all directives taking a boolean argument. Both flags will ensure that a directive takes one argument.
* Overhauled diagnostic messages.Ruslan Ermilov2011-09-19
|
* Fixing Linux AIO initiatialization: AIO operations are disabled if kernelIgor Sysoev2011-09-16
| | | | does not support them. Previously worker just exited.
* Fixing Linux AIO syscalls return value handling:Igor Sysoev2011-09-16
| | | | | | | syscall(2) uses usual libc convention, it returns -1 on error and sets errno. Obsolete _syscall(2) returns negative value of error. Thanks to Hagai Avrahami.
* Trailing space fix.Maxim Dounin2011-09-16
|
* Upstream keepalive module.Maxim Dounin2011-09-15
|
* Proxy: basic HTTP/1.1 support (including keepalive).Maxim Dounin2011-09-15
| | | | | By default we still send requests using HTTP/1.0. This may be changed with new proxy_http_version directive.
* Protocol version parsing in ngx_http_parse_status_line().Maxim Dounin2011-09-15
| | | | | Once we know protocol version, set u->headers_in.connection_close to indicate implicitly assumed connection close with HTTP before 1.1.
* Upstream: Connection header processing.Maxim Dounin2011-09-15
|
* Upstream: Transfer-Encoding header processing.Maxim Dounin2011-09-15
|
* Keepalive support in fastcgi.Maxim Dounin2011-09-15
| | | | | | By default follow the old behaviour, i.e. FASTCGI_KEEP_CONN flag isn't set in request and application is responsible for closing connection once request is done. To keep connections alive fastcgi_keep_conn must be activated.
* Keepalive support in memcached.Maxim Dounin2011-09-15
|
* Upstream: keepalive flag.Maxim Dounin2011-09-15
| | | | | This patch introduces r->upstream->keepalive flag, which is set by protocol handlers if connection to upstream is in good state and can be kept alive.
* Upstream: pipe length and input_filter_init in buffered mode.Maxim Dounin2011-09-15
| | | | | | | | | | | | As long as ngx_event_pipe() has more data read from upstream than specified in p->length it's passed to input filter even if buffer isn't yet full. This allows to process data with known length without relying on connection close to signal data end. By default p->length is set to -1 in upstream module, i.e. end of data is indicated by connection close. To set it from per-protocol handlers upstream input_filter_init() now called in buffered mode (as well as in unbuffered mode).
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-18 09:17:14 +0000