summaryrefslogtreecommitdiffhomepage
AgeCommit message (Collapse)AuthorFilesLines
2018-10-09Renamed "go" application type to "external".Valentin Bartenev17-88/+91
There's nothing specific to Go language. This type of application object can be used to run any external application that utilizes libunit API.
2018-10-05Packages: all CRLF newlines in examples converted to LF.Andrei Belov6-126/+126
2018-10-03Added Node.js support.Alexander Borisov13-0/+1667
2018-10-02Filling cmsghdr with 0 to pass Go 1.11 message validation.Max Romanov1-4/+5
2018-10-02Go: fixing typo in log messages.Max Romanov2-2/+2
2018-10-02Making port fd blocking on app side and non-blocking in Unit.Max Romanov2-1/+12
This issue was introduced in libunit commit (e0f0cd7d244a). All port sockets in application should be in blocking mode whereas Unit itself operates non-blocking sockets. Having non-blocking sockets in application may cause send error during intensive response packets generation. See https://mailman.nginx.org/pipermail/unit/2018-October/000080.html.
2018-10-01Disabled chunked transfer encoding for 304 responses as well.Valentin Bartenev1-1/+1
According to RFC 7232: | A 304 response cannot contain a message-body; it is always terminated | by the first empty line after the header fields.
2018-10-01Allowing keep-alive connections after 204 responses.Valentin Bartenev1-5/+7
This was unintentionally disabled by 7b5026a0bdeb.
2018-10-01Fixed error log time caching resolution.Valentin Bartenev1-1/+1
Thanks to 洪志道 (Hong Zhi Dao).
2018-10-01Mention of --openssl configure option in help.Valentin Bartenev1-0/+2
This closes #171 issue on GitHub. Thanks to 洪志道 (Hong Zhi Dao).
2018-10-01Skipping minor entries while producing generic CHANGES.Andrei Belov2-0/+10
Currently we consider any changes with revision other than 1 as packages-specific, thus there is no need to include such entries to the generic Unit change log.
2018-09-28Disabled chunked transfer encoding for 204 responses.Igor Sysoev3-2/+3
2018-09-28Fixed bug in socket write error handling.Igor Sysoev1-1/+3
The bug has been introduced in e3972a4a9c73.
2018-09-28Version bump.Valentin Bartenev1-2/+2
2018-09-27Packages: updated to 1.4-2.Andrei Belov35-34/+66
2018-09-27Packages: adjusted post-install banners.Andrei Belov22-27/+49
2018-09-26Packages: removed "loadconfig" and "saveconfig" actions.Andrei Belov5-118/+4
2018-09-20Added tag 1.4 for changeset 8f4524a9cf87Valentin Bartenev1-0/+1
2018-09-20Generated Dockerfiles for Unit 1.4.1.4Valentin Bartenev9-9/+9
2018-09-20Added version 1.4 CHANGES.Valentin Bartenev2-0/+116
2018-09-20Resetting init->stream for ready process.Max Romanov1-0/+4
Router requests application start by sending port message with application parameters to master. In response router gets application port. Stream id used to link request and response. If application process terminates unexpectedly (e.g. before ready state), it is required to notify router about application start failure. For this purpose stream id is stored in process initialization parameters. Stream id sequentially incremented and starts from 1 in case of router resurrection. New router application start stream id may coincide with stream id of currently running/terminating application processes. In such cases router may receive REMOVE_PID message with same stream id as used in application start request and mistakenly reports application start failure. This commit tries to avoid such errors by resetting stream for processes in ready state.
2018-09-20Tests: TLS tests.Andrey Zelenkov2-4/+505
2018-09-20Fixed building perl on Alpine Linux.Sergey Kandaurov2-0/+3
_GNU_SOURCE is required there to expose off64_t and other types.
2018-09-20Preventing port from release in asynchronous operations.Max Romanov1-0/+12
Router reconfiguration may lead to starting new application processes, opening listen ports etc. These actions are asynchronous and require message exchange with master process. Router stores reference for controller (response) port in structure associated with reconfiguration process (tmcf). The port used to provide reconfiguration response (either success or failed) to controller. This commit increases response port use counter to make sure port structure not freed while router waits for result of asynchronous operations.
2018-09-20Packages: enabled OpenSSL support.Andrei Belov4-7/+13
2018-09-20Python: adjusted input.read(size) argument value interpretation.Valentin Bartenev2-4/+5
Previously, passing 0 resulted in reading the whole body and all negative values raised an exception. Now the behaviour is in consistentance with io.RawIOBase.read() interface, and passing 0 returns empty (byte) string, while -1 results in reading the whole body.
2018-09-20Preserving inherited engine memory pool in controller process.Max Romanov1-8/+0
The pool is inherited from master process since changeset 854a1a440616.
2018-09-20Controller: addressing of array elements in requests.Valentin Bartenev1-1/+20
2018-09-20Controller: certificates storage interface.Valentin Bartenev16-44/+2103
2018-09-20Deduplicated string value initializations.Valentin Bartenev2-64/+23
2018-09-20Added nginx error 497 response.Igor Sysoev2-0/+22
2018-09-20Added SSL/TLS support on connection level.Igor Sysoev22-600/+926
2018-09-19Initializing application structure with 0 to avoid crash.Max Romanov1-2/+7
Attribute 'application' is optional in listener object. This commit adds missing code to reset 'lscf' to avoid garbage and crash when the attribute is absent.
2018-09-19Initializing user_cred gids and ngroups for MacOS.Max Romanov1-0/+4
2018-09-18Fixed more typos.Valentin Bartenev2-2/+2
Thanks to 洪志道 (Hong Zhi Dao).
2018-09-17Tests: test_settings_header_read_timeout_update adjusted.Andrey Zelenkov1-4/+9
2018-09-17Fixed non-auto-reset timers.Igor Sysoev1-10/+5
2018-09-17Removed deprecated MacOSX OSSpinLockLock().Igor Sysoev3-80/+2
2018-09-17Fixed typo.Igor Sysoev1-1/+1
This closes #166 issue on GitHub. Thanks to 洪志道 (Hong Zhi Dao).
2018-09-17Fixed typo.Igor Sysoev1-1/+1
This closes #165 issue on GitHub. Thanks to 洪志道 (Hong Zhi Dao).
2018-09-10Fixed spelling in a comment.Valentin Bartenev1-1/+1
This closes #161 issue on GitHub. Thanks to 洪志道 (Hong Zhi Dao).
2018-09-07Misspelled variable names fixed.Max Romanov4-7/+7
2018-09-06Tests: used relative path for configuration.Andrey Zelenkov11-126/+125
2018-09-04Tests: fixed test_settings_header_read_timeout_update.Andrey Zelenkov1-4/+7
2018-09-04Tests: "no_recv" option introduced.Andrey Zelenkov1-2/+5
2018-09-04Tests: "/config" prefix used.Andrey Zelenkov1-3/+12
2018-08-21Tests: more timeout tests.Andrey Zelenkov1-0/+51
2018-08-21Tests: typo.Andrey Zelenkov1-1/+1
2018-08-10Stopping all application processes if router process dies.Max Romanov3-3/+29
Unit master process restarts the router if the router accidentally dies. New router process receives the configuration from controller and starts configured applications. The information of running applications cannot be transferred to router because currently there is no persistent application identifier. To avoid orphan application processes started by died router, master process stops all currently running applications once it receives SIGCHLD for router process.
2018-08-10Introducing app joint to accurate app release.Max Romanov4-94/+169
For accurate app descriptor release, it is required to count the number of use counts. Use count increased when: - app linked to configuration app queue; - socket conf stores pointer to app; - request for start app process posted to router service thread; Application port has pointer to app, but it does not increase use count to avoid use count loop. Timer needs a pointer to nxt_timer_t which is stored in engine timers tree. nxt_timer_t now resides in nxt_app_joint_t and does not lock the application. Start process port RPC handlers is also linked to nxt_app_joint_t. App joint (nxt_app_joint_t) is a 'weak pointer': - single threaded; - use countable; - store pointer to nxt_app_t (which can be NULL); nxt_app_t has pointer to nxt_app_joint_t and update its pointer to app.
generated by cgit (git 2.34.1) at 2024-11-18 15:26:26 +0000