aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Improved check for duplicate path names in ngx_add_path().Valentin Bartenev2013-09-16
| | | | | | | | | The same path names with different "data" context should not be allowed. In particular it rejects configurations like this: proxy_cache_path /var/cache/ keys_zone=one:10m max_size=1g inactive=5m; proxy_cache_path /var/cache/ keys_zone=two:20m max_size=4m inactive=30s;
* Removed surplus initializations from ngx_conf_set_path_slot().Valentin Bartenev2013-09-16
| | | | An instance of ngx_path_t is already zeroed by ngx_pcalloc().
* Use ngx_pcalloc() in ngx_conf_merge_path_value().Valentin Bartenev2013-09-16
| | | | | It initializes the "data" pointer of ngx_path_t that will be checked after subsequent changes.
* Use EPOLLRDHUP in ngx_http_test_reading() (ticket #320).Valentin Bartenev2013-09-16
| | | | | This allows to detect client connection close with pending data when the ngx_http_test_reading() request event handler is set.
* Upstream: use EPOLLRDHUP to check broken connections (ticket #320).Valentin Bartenev2013-09-16
| | | | | This allows to detect client connection close with pending data on Linux while processing upstream.
* Events: support for EPOLLRDHUP (ticket #320).Valentin Bartenev2013-07-12
| | | | | Since Linux 2.6.17, epoll is able to report about peer half-closed connection using special EPOLLRDHUP flag on a read event.
* Events: removed unused flags from the ngx_event_s structure.Valentin Bartenev2013-09-05
| | | | They are not used since 708f8bb772ec (pre 0.0.1).
* Fixed handling of the ready flag with kqueue.Valentin Bartenev2013-09-05
| | | | | There is nothing to do more when recv() has returned 0, so we should drop the flag.
* Return reason phrase for 414.Valentin Bartenev2013-09-03
| | | | After 62be77b0608f nginx can return this code.
* Upstream: fixed $upstream_response_time format specifiers.Maxim Dounin2013-09-04
|
* SSL: clear error queue after SSL_CTX_load_verify_locations().Maxim Dounin2013-09-04
| | | | | | | The SSL_CTX_load_verify_locations() may leave errors in the error queue while returning success (e.g. if there are duplicate certificates in the file specified), resulting in "ignoring stale global SSL error" alerts later at runtime.
* Fixed incorrect response line on "return 203".Maxim Dounin2013-09-04
| | | | | Reported by Weibin Yao, http://mailman.nginx.org/pipermail/nginx-devel/2013-April/003607.html.
* Request cleanup code unified, no functional changes.Maxim Dounin2013-09-04
| | | | | Additionally, detaching a cleanup chain from a request is a bit more resilent to various bugs if any.
* Handling of ngx_int_t != intptr_t case.Maxim Dounin2013-09-04
| | | | | | | | | Casts between pointers and integers produce warnings on size mismatch. To silence them, cast to (u)intptr_t should be used. Prevoiusly, casts to ngx_(u)int_t were used in some cases, and several ngx_int_t expressions had no casts. As of now it's mostly style as ngx_int_t is defined as intptr_t.
* Win32: $request_time fixed.Maxim Dounin2013-09-04
| | | | | | On win32, time_t is 64 bits wide by default, and passing an ngx_msec_int_t argument for %T format specifier doesn't work. This doesn't manifest itself on other platforms as time_t and ngx_msec_int_t are usually of the same size.
* Win32: MinGW GCC compatibility.Maxim Dounin2013-09-04
| | | | | | | | | Several warnings silenced, notably (ngx_socket_t) -1 is now checked on socket operations instead of -1, as ngx_socket_t is unsigned on win32 and gcc complains on comparison. With this patch, it's now possible to compile nginx using mingw gcc, with options we normally compile on win32.
* Win32: Borland C compatibility fixes.Maxim Dounin2013-09-04
| | | | | | | | | | Several false positive warnings silenced, notably W8012 "Comparing signed and unsigned" (due to u_short values promoted to int), and W8072 "Suspicious pointer arithmetic" (due to large type values added to pointers). With this patch, it's now again possible to compile nginx using bcc32, with options we normally compile on win32 minus ipv6 and ssl.
* Win32: Open Watcom C compatibility fixes.Maxim Dounin2013-09-04
| | | | | | | | | Precompiled headers are disabled as they lead to internal compiler errors with long configure lines. Couple of false positive warnings silenced. Various win32 typedefs are adjusted to work with Open Watcom C 1.9 headers. With this patch, it's now again possible to compile nginx using owc386, with options we normally compile on win32 minus ipv6 and ssl.
* Disable symlinks: removed recursive call of ngx_file_o_path_info().Valentin Bartenev2013-09-02
| | | | It is surplus.
* Disable symlinks: use O_PATH to open path components.Valentin Bartenev2013-09-02
| | | | | | | | | | | | | | | | | It was introduced in Linux 2.6.39, glibc 2.14 and allows to obtain file descriptors without actually opening files. Thus made it possible to traverse path with openat() syscalls without the need to have read permissions for path components. It is effectively emulates O_SEARCH which is missing on Linux. O_PATH is used in combination with O_RDONLY. The last one is ignored if O_PATH is used, but it allows nginx to not fail when it was built on modern system (i.e. glibc 2.14+) and run with a kernel older than 2.6.39. Then O_PATH is unknown to the kernel and ignored, while O_RDONLY is used. Sadly, fstat() is not working with O_PATH descriptors till Linux 3.6. As a workaround we fallback to fstatat() with the AT_EMPTY_PATH flag that was introduced at the same time as O_PATH.
* Added the NGX_EBADF define.Valentin Bartenev2013-09-02
|
* Assume the HTTP/1.0 version by default.Valentin Bartenev2013-09-02
| | | | | | | | | | | It is believed to be better than fallback to HTTP/0.9, because most of the clients at present time support HTTP/1.0. It allows nginx to return error response code for them in cases when it fail to parse request line, and therefore fail to detect client protocol version. Even if the client does not support HTTP/1.0, this assumption should not cause any harm, since from the HTTP/0.9 point of view it still a valid response.
* Upstream: setting u->header_sent before ngx_http_upstream_upgrade().Maxim Dounin2013-08-30
| | | | | | Without u->header_sent set a special response might be generated following an upgraded connection. The problem appeared in 1ccdda1f37f3 (1.5.3). Catched by "header already sent" alerts in 1.5.4 after upstream timeouts.
* Referer: fixed hostname buffer overflow check.Valentin Bartenev2013-08-29
| | | | | Because of premature check the effective buffer size was 255 symbols while the buffer is able to handle 256.
* Referer: "server_names" parsing deferred to merge phase.Sergey Kandaurov2013-08-29
| | | | | | | | | | | This allows to approach "server_name" values specified below the "valid_referers" directive when used within the "server_names" parameter, e.g.: server_name example.org; valid_referers server_names; server_name example.com; As a bonus, this fixes bogus error with "server_names" specified several times.
* Referer: fixed server_name regex matching.Sergey Kandaurov2013-08-29
| | | | | | | | | | | | | | | | | | | The server_name regexes are normally compiled for case-sensitive matching. This violates case-insensitive obligations in the referer module. To fix this, the host string is converted to lower case before matching. Previously server_name regex was executed against the whole referer string after dropping the scheme part. This could led to an improper matching, e.g.: server_name ~^localhost$; valid_referers server_names; Referer: http://localhost/index.html It was changed to look only at the hostname part. The server_name regexes are separated into another array to not clash with regular regexes.
* Referer: fixed error type usage inconsistency for ngx_http_add*().Sergey Kandaurov2013-08-29
|
* Image filter: large image handling.Lanshun Zhou2013-08-28
| | | | | | | | | | If Content-Length header is not set, and the image size is larger than the buffer size, client will hang until a timeout occurs. Now NGX_HTTP_UNSUPPORTED_MEDIA_TYPE is returned immediately. diff -r d1403de41631 -r 4fae04f332b4 src/http/modules/ngx_http_image_filter_module.c
* Typo fixed.Maxim Dounin2013-08-28
|
* Version bump.Maxim Dounin2013-08-28
|
* Cache: lock timeouts are now logged at info level.Maxim Dounin2013-08-23
|
* Upstream: posted requests handling after ssl handshake errors.Maxim Dounin2013-08-23
| | | | | | | Missing call to ngx_http_run_posted_request() resulted in a main request hang if subrequest's ssl handshake with an upstream server failed for some reason. Reported by Aviram Cohen.
* Fixed try_files with empty argument (ticket #390).Maxim Dounin2013-08-23
|
* Added safety belt for the case of sending header twice.Sergey Kandaurov2013-07-30
| | | | | The aforementioned situation is abnormal per se and as such it now forces request termination with appropriate error message.
* Autoindex: improved ngx_de_info() error handling.Sergey Kandaurov2013-07-30
| | | | | This allows to build a directory listing whenever a loop exists in symbolic link resolution of the path argument.
* Autoindex: return NGX_ERROR on error if headers were sent.Sergey Kandaurov2013-07-30
| | | | | This prevents ngx_http_finalize_request() from issuing ngx_http_special_response_handler() on a freed context.
* Style improved after 12dd27b74117.Maxim Dounin2013-08-20
|
* Backed out f1a91825730a and 7094bd12c1ff.Maxim Dounin2013-08-20
| | | | | | | While ngx_get_full_name() might have a bit more descriptive arguments, the ngx_conf_full_name() is generally easier to use when parsing configuration and limits exposure of cycle->prefix / cycle->conf_prefix details.
* Auth request module import.Maxim Dounin2013-08-21
|
* Minor ngx_http_parse_request_line() optimization.Maxim Dounin2013-08-21
| | | | Noted by Nils Kuhnhenn.
* Format specifier fixes in error logging.Sergey Kandaurov2013-08-20
|
* SPDY: alert about activated fake events instead of deleting them.Valentin Bartenev2013-08-15
| | | | | | | | | They refer to the same socket descriptor as our real connection, and deleting them will stop processing of the connection. Events of fake connections must not be activated, and if it happened there is nothing we can do. The whole processing should be terminated as soon as possible, but it is not obvious how to do this safely.
* SPDY: do not reject headers with empty value (ticket #396).Valentin Bartenev2013-08-15
| | | | | | | | | | | | | | | A quote from SPDY draft 2 specification: "The length of each name and value must be greater than zero. A receiver of a zero-length name or value must send a RST_STREAM with code PROTOCOL error." But it appears that Chrome browser allows sending requests over SPDY/2 connection using JavaScript that contain headers with empty values. For better compatibility across SPDY clients and to be compliant with HTTP, such headers are no longer rejected. Also, it is worth noting that in SPDY draft 3 the statement has been changed so that it permits empty values for headers.
* SPDY: fixed corruption of headers with names longer than 255.Valentin Bartenev2013-08-15
| | | | | It is a bad idea to put zero byte in position where the length of the next header name can be stored before it was parsed.
* Unbreak building on Linux without sendfile64() support.Valentin Bartenev2013-08-15
| | | | | | | | | | | | It was broken in 8e446a2daf48 when the NGX_SENDFILE_LIMIT constant was added to ngx_linux_sendfile_chain.c having the same name as already defined one in ngx_linux_config.h. The newer is needed to overcome a bug in old Linux kernels by limiting the number of bytes to send per sendfile() syscall. The older is used with sendfile() on ancient kernels that works with 32-bit offsets only. One of these renamed to NGX_SENDFILE_MAXSIZE.
* Referer module: fixed regex matching against HTTPS referers.Sergey Kandaurov2013-08-13
| | | | | | | | When matching a compiled regex against value in the "Referer" header field, the length was calculated incorrectly for strings that start from "https://". This might cause matching to fail for regexes with end-of-line anchors. Patch by Liangbin Li.
* Don't lose pointer to first nonempty buf in ngx_*_sendfile_chain().Gleb Smirnoff2013-08-08
| | | | | | | | In ngx_*_sendfile_chain() when calculating pointer to a first non-zero sized buf, use "in" as iterator. This fixes processing of zero sized buf(s) after EINTR. Otherwise function can return zero sized buf to caller, and later ngx_http_write_filter() logs warning.
* API change: removed the ngx_conf_full_name() function.Valentin Bartenev2013-08-06
| | | | The ngx_get_full_name() should be used instead.
* Replaced ngx_conf_full_name() with ngx_get_full_name().Valentin Bartenev2013-08-06
| | | | The ngx_get_full_name() function takes more readable arguments list.
* Fixed memory leaks in the root and auth_basic_user_file directives.Valentin Bartenev2013-08-06
| | | | | | | | If a relative path is set by variables, then the ngx_conf_full_name() function was called while processing requests, which causes allocations from the cycle pool. A new function that takes pool as an argument was introduced.