summaryrefslogtreecommitdiffhomepage
path: root/src (follow)
AgeCommit message (Collapse)AuthorFilesLines
2019-05-30Fixed segfault with empty rule array.Igor Sysoev1-3/+3
2019-05-30Java: fixing typo in context initialization.Max Romanov1-1/+1
2019-05-30Java: fixing request scheme using 'tls' flag.Max Romanov2-2/+6
2019-04-24Configuration: support for POST operations on arrays.Valentin Bartenev3-20/+74
It allows to add an array element without specifying the index.
2019-04-24Configuration: support for manipulations of array elements.Valentin Bartenev1-29/+141
Now PUT and DELETE operations also work on elements. This closes #242 issue on GitHub.
2019-04-24Refactored nxt_conf_op_compile().Valentin Bartenev1-7/+8
Now index is always initialized for create operations. The changes in nxt_conf_op_compile() simplify adding upcoming support of operations with arrays. No functional changes.
2019-04-24Removed unused field from nxt_conf_op_s.Valentin Bartenev1-2/+1
2019-04-17Node.js: using low-case header names as key in req.headers.Max Romanov1-4/+17
Node.js modules (body-parser, row-body) search low-cased names ('content-length', 'content-type' etc.) to properly assemble request body. This closes #246 issue on GitHub.
2019-04-12Controller: rejecting double wildcards.Valentin Bartenev1-1/+6
2019-04-12Simplified cycles in nxt_http_route_rule().Valentin Bartenev1-40/+24
2019-04-10Added support for wildcards in the middle of match patterns.Igor Sysoev2-24/+129
2019-04-03Backed out changeset f74d4dd9c3db.Valentin Bartenev1-0/+8
This closes #240 issue on GitHub.
2019-04-02Removing unused variables and assignments.Max Romanov1-8/+5
Warnings introduced in 53533ba0097c commit.
2019-04-01Adding 'connection' to request as an alias to 'socket'.Max Romanov1-4/+11
Adding actual 'remoteAddress' and 'localAddress' into socket object. This closes #232 issue on GitHub.
2019-04-01Introducing close event to notify about server stop.Max Romanov2-0/+25
This closes #236 on GitHub. Thanks to 0xcdcdcdcd.
2019-04-01Adding syntax sugar.Max Romanov5-654/+882
With exceptions and overloads.
2019-03-25Turning off port read event state after main process fork.Max Romanov1-0/+1
Master port stores two file descriptors and works as a read port on the master process side. After a fork, the port switches into write mode and the read socket closes, but the same event structure is used for the write socket. However, the inherited structure remained in read state, telling the epoll engine to use MOD operation instead of ADD. The patch resets read event state, so the engine may write using proper ADD operation.
2019-03-22Ignoring EPERM error when changing application process uid/gid.Max Romanov1-16/+33
This closes #228 issue on GitHub.
2019-03-22Destroying pool in case of error.Max Romanov2-2/+2
This closes #233 issue on GitHub. Thanks to 洪志道 (Hong Zhi Dao).
2019-03-22Style fixing.Max Romanov1-0/+1
This closes #233 issue on GitHub. Thanks to 洪志道 (Hong Zhi Dao).
2019-03-21Adjusting request schema value according to connection tls state.Max Romanov13-31/+82
This closes #223 issue on GitHub.
2019-03-18Removing unused local variable.Max Romanov1-7/+0
2019-03-18Setting request error flag in error handler.Max Romanov1-0/+2
Absence of this flag is the reason of memory leak in case when client disconnected before receiving all response data.
2019-03-11Style.Andrey Zelenkov20-48/+48
2019-03-06Removed unnecessary abstraction layer.Alexander Borisov6-260/+127
2019-03-05Improving port message fragment recognition.Max Romanov1-16/+36
This is required to assemble fragmented messages correctly. Stream identifier is unique only for messages generated within a process, but the (stream, pid) pair should be enough to avoid collisions. Adding reply_port seems redundant because it's enough to add stream to a pid. This closes #199 issue on GitHub. Thanks to 洪志道 (Hong Zhi Dao).
2019-03-05Fixing EAGAIN processing for port message send.Max Romanov1-8/+26
Sending large plain (exceeding port's max_size, not in shared memory) messages causes message fragmentation. First message fragment is sent successfully, but the next fragment may fail with the EAGAIN error. In this case, the message has to be pushed back to queue head for additional processing. Related to #167 issue on GitHub.
2019-03-05Handling ENOBUFS error same was as EAGAIN.Max Romanov2-2/+12
Unlike EAGAIN, ENOBUFS returned on OSX when trying to send many relatively small (64 bytes) fragments. Found during investigation of #167 issue on GitHub.
2019-03-05Including port message header into message size limit.Max Romanov1-0/+2
Before this fix, large plain message (i.e. configuration) send may fail with the 'Message too big' error, because internal fragmentation implementation does not account for 16 byte message header. This closes #167 issue on GitHub.
2019-03-01Fixed TLS connections hanging.Igor Sysoev1-4/+2
After event is delivered from the kernel its further processing is blocked. Non-ready TSL I/O operation should mark connection I/O state as not ready to unblock events and to allow their further processing. Otherwise the connection hangs.
2019-03-01README.JSR-340 legal notice to save our ughm.. bottoms of bodies.Valentin Bartenev1-0/+16
2019-03-01Perl: added implementation delayed response and streaming body.Alexander Borisov1-16/+176
2019-02-28Made QUERY_STRING mandatory.Valentin Bartenev4-17/+7
According to CGI/1.1 RFC 3875: The server MUST set this variable; if the Script-URI does not include a query component, the QUERY_STRING MUST be defined as an empty string (""). Python's PEP 333(3) allows omitting it in WSGI interface; PHP docs force no requirements; PSGI and Rack specifications require it even if empty. When nginx proxies requests over FastCGI, it always provides QUERY_STRING. and some PHP apps have been observed to fail if it is missing (see issue #201 on GitHub). A drawback of this change (besides a small overhead) is that there will be no easy way to tell a missing query string from an empty one (i.e. requests with or without the "?" character); yet, it's negligible compared to the possible benefits of wider application compatibility. This closes #226 issue on GitHub.
2019-02-28Fixed timer and event race condition.Igor Sysoev5-8/+17
When idle timeout occurs at the same time as a request comes in, the timer handler closes connection while the read event triggers request processing, and this eventually leads to segmentation fault.
2019-02-28Preserving message 'share' field when pushing to queue.Max Romanov1-0/+1
As far as I understand, this field is important to control the number of buffers send in a single write attempt. Furthermore, having uninitialized field is always bad. This closes #204 issue on GitHub. Thanks to 洪志道 (Hong Zhi Dao).
2019-02-28Introducing Java Servlet Container beta.Max Romanov51-1/+10694
2019-02-28Various libunit fixes.Max Romanov1-8/+26
This patch contains various logging improvements and bugfixes found during Java module development.
2019-02-28Removing app data debug message.Max Romanov1-4/+0
This message produces too many noise in log and complicates analysis.
2019-02-28Reusing fragmented message buffers.Max Romanov1-1/+9
Fragmented message non-mmap buffer chain not freed nor reused before this fix. This closes #206 on GitHub. Thanks to 洪志道 (Hong Zhi Dao).
2019-02-27Perl: added processing for IO:Handle-like object.Alexander Borisov1-3/+109
The application can return the body as an IO:Handle-like object without file descriptor.
2019-02-27Fixed processing of SERVER_NAME after 77aad2c142a0.Valentin Bartenev11-167/+54
Previously, the nxt_router_prepare_msg() function expected server host among other headers unmodified. It's not true anymore since normalization of the Host header has been introduced in 77aad2c142a0. The nxt_unit_split_host() function was removed. It didn't work correctly with IPv6 literals. Anyway, after 77aad2c142a0 the port splitting is done in router while Host header processing.
2019-02-27Controller: added "routes" configuration.Valentin Bartenev1-0/+186
2019-02-27Controller: added "pass" configuration option.Valentin Bartenev1-0/+62
2019-02-27Initial routing implementation.Igor Sysoev5-40/+978
2019-02-26Introduced nxt_memcpy_upcase().Igor Sysoev2-0/+15
2019-02-26Introduced nxt_conf_array_qsort().Igor Sysoev2-0/+18
2019-02-26Introduced nxt_conf_array_elements_count().Igor Sysoev2-0/+8
2019-02-26Keepalive mode is disabled on HTTP header parsing errors.Igor Sysoev1-0/+2
2019-02-26Fixed violation of the strict aliasing rules in 5d0edd35c4ce.Valentin Bartenev1-5/+6
In order to reduce number of operations over rb-tree and process them in batches simultaneously, all the timers changes are temporary stored in array. While processing of these changes, the same memory is also used for storing pointers to postpone timers adding. As the same block of memory has been referenced by two different types of pointers (nxt_timer_change_t * and nxt_timer_t **), some compilers may reorder operations with these pointers and produce broken code. See ticket #221 on GitHub for a particular case. Now the same "nxt_timer_change_t" structure is used in both cases. Also, reverted the -fno-strict-aliasing flag, which has been introduced in ef76227ec159 as a workaround for this issue.
2019-02-25RPC error message size fixed.Max Romanov1-1/+1
In case of RPC error, special error message passed to handler. Field 'size' expected to be 0 in this case because in contains fake empty buffer.
generated by cgit (git 2.34.1) at 2024-11-17 14:21:58 +0000