History log of /unit/docs/changes.xml (Results 26 – 50 of 288)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 2523:1c466e280eb0 22-Aug-2023 Konstantin Pavlov

Docs: added changelogs for unit-wasm.


# 2512:5e9e70378c1d 09-Aug-2023 Zhidao HONG

HTTP: controlling response headers support.


# 2505:450bf52c3a2c 30-Jun-2023 Zhidao HONG

Var: supported HTTP response header variables.

This commit adds the variable $response_header_NAME.


# 2503:6529f5fa9d9a 11-Jul-2023 Zhidao HONG

NJS: supported 0.8.0.


# 2489:b37326158d10 24-May-2023 Zhidao HONG

HTTP: fixed variable caching.

When a variable is accessed in the Unit configuration, the value is cached.
This was useful prior to the URI rewrite feature, but now that the URI (more
precisely, the

HTTP: fixed variable caching.

When a variable is accessed in the Unit configuration, the value is cached.
This was useful prior to the URI rewrite feature, but now that the URI (more
precisely, the request target) can be rewritten, the contents of the variable
$uri (which contains the path part of the request target, and is decoded)
should not be cached anymore, or at least the cached value should be invalidated
after a URI rewrite.

Example:

{
"rewrite": "/prefix$uri",
"share": "$uri"
}

For a request line like GET /foo?bar=baz HTTP/1.1\r\n, the expected file
served in the response would be /prefix/foo, but due to the caching issue,
Unit currently serves /foo.

show more ...


# 2474:00f56c19efeb 24-May-2023 Andrei Zeliankou

Version bump.


Revision tags: 1.30.0-1
# 2464:8a0b4338a156 10-May-2023 Konstantin Pavlov

Merged with the default branch.


Revision tags: 1.30.0
# 2461:e9af09885db1 10-May-2023 Andrei Zeliankou

Added version 1.30.0 CHANGES.


# 2460:41e40e19b174 10-May-2023 Andrei Zeliankou

Edited "changes.xml" for the 1.30.0 release.


# 2452:751880f06069 03-May-2023 Konstantin Pavlov

Packages: added Ubuntu 23.04 "lunar" support.


# 2450:14277f21a722 08-May-2023 Zhidao HONG

NJS: supported loadable modules.


# 2448:243735980417 20-Apr-2023 Zhidao HONG

HTTP: added basic URI rewrite.

This commit introduced the basic URI rewrite. It allows users to change request URI. Note the "rewrite" option ignores the contained query if any and the query from th

HTTP: added basic URI rewrite.

This commit introduced the basic URI rewrite. It allows users to change request URI. Note the "rewrite" option ignores the contained query if any and the query from the request is preserverd.
An example:
"routes": [
{
"match": {
"uri": "/v1/test"
},
"action": {
"return": 200
}
},
{
"action": {
"rewrite": "/v1$uri",
"pass": "routes"
}
}
]

Reviewed-by: Alejandro Colomar <alx@nginx.com>

show more ...


# 2381:a68b5f5bf46c 26-Jan-2023 Alejandro Colomar

HTTP: added route logging.

- Configuration: added "/config/settings/http/log_route".

Type: bool
Default: false

This adds configurability to the error log. It allows enabling and
disa

HTTP: added route logging.

- Configuration: added "/config/settings/http/log_route".

Type: bool
Default: false

This adds configurability to the error log. It allows enabling and
disabling logs related to how the router performs selection of the
routes.

- HTTP: logging request line.

Log level: [notice]

The request line is essential to understand which logs correspond to
which request when reading the logs.

- HTTP: logging route that's been discarded.

Log level: [info]

- HTTP: logging route whose action is selected.

Log level: [notice]

- HTTP: logging when "fallback" action is taken.

Log level: [notice]

Closes: <https://github.com/nginx/unit/issues/758>
Link: <https://github.com/nginx/unit/pull/824>
Link: <https://github.com/nginx/unit/pull/839>
Suggested-by: Timo Stark <t.stark@nginx.com>
Suggested-by: Mark L Wood-Patrick <mwoodpatrick@gmail.com>
Suggested-by: Liam Crilly <liam@nginx.com>
Tested-by: Liam Crilly <liam@nginx.com>
Acked-by: Artem Konev <a.konev@f5.com>
Cc: Andrew Clayton <a.clayton@nginx.com>
Cc: Andrei Zeliankou <zelenkov@nginx.com>
Reviewed-by: Zhidao Hong <z.hong@f5.com>
Signed-off-by: Alejandro Colomar <alx@nginx.com>

show more ...


# 2367:7549958dbc33 01-Mar-2023 Andrei Zeliankou

Merged with the 1.29 branch.


Revision tags: 1.29.1-1
# 2364:ad98bd4c52da 28-Feb-2023 Konstantin Pavlov

Merged with the 1.29 branch.


Revision tags: 1.29.1
# 2361:406d1ae27425 28-Feb-2023 Andrei Zeliankou

Added version 1.29.1 CHANGES.


# 2360:16365e6bb6d7 28-Feb-2023 Andrei Zeliankou

Changes moved to the correct section.


# 2359:b9cacd1ac37d 28-Feb-2023 Andrei Zeliankou

Added missing fixes in changes.xml.


# 2358:9dce85e82513 28-Feb-2023 Andrei Zeliankou

Added missing fixes in changes.xml.


# 2345:5c9cb7e205d3 30-Jan-2023 Zhidao HONG

NJS: adding the missing vm destruction.

This commit fixed the njs memory leak happened in the config validation, updating and http requests.


# 2335:6f30c434cca9 15-Dec-2022 Konstantin Pavlov

Docs: added changelog for Python 3.11.

While at it, fixed changelogs generation for Python 3.10 as well.


# 2334:2d8a18fde53b 27-Feb-2023 Andrei Zeliankou

Version bump.


# 2318:6f198d76ee62 30-Jan-2023 Zhidao HONG

NJS: adding the missing vm destruction.

This commit fixed the njs memory leak happened in the config validation, updating and http requests.


# 2314:bc5a90e2e6e8 14-Jul-2022 Alejandro Colomar

Added default values for pathnames.

This allows one to simply run `./configure` and expect it to
produce sane defaults for an install.

Previously, without specifying `--prefix=...`, `make install`

Added default values for pathnames.

This allows one to simply run `./configure` and expect it to
produce sane defaults for an install.

Previously, without specifying `--prefix=...`, `make install`
would simply fail, recommending to set `--prefix` or `DESTDIR`,
but that recommendation was incomplete at best, since it didn't
set many of the subdirs needed for a good organization.

Setting `DESTDIR` was even worse, since that shouldn't even affect
an installation (it is required to be transparent to the
installation).

/usr/local is the historic Unix standard path to use for
installations from source made manually by the admin of the
system. Some package managers (Homebrew, I'm looking specifically
at you) have abused that path to install their things, but 1) it's
not our fault that someone else incorrectly abuses that path (and
they seem to be fixing it for newer archs; e.g., they started
using /opt/homebrew for Apple Silicon), 2) there's no better path
than /usr/local, 3) we still allow changing it for systems where
this might not be the desired path (MacOS Intel with hombrew), and
4) it's _the standard_.

See a related conversation with Ingo (OpenBSD maintainer):

On 7/27/22 16:16, Ingo Schwarze wrote:
> Hi Alejandro,
[...]
>
> Alejandro Colomar wrote on Sun, Jul 24, 2022 at 07:07:18PM +0200:
>> On 7/24/22 16:57, Ingo Schwarze wrote:
>>> Alejandro Colomar wrote on Sun, Jul 24, 2022 at 01:20:46PM +0200:
>
>>>> /usr/local is for sysadmins to build from source;
>
>>> Doing that is *very* strongly discouraged on OpenBSD.
>
>> I guess that's why the directory was reused in the BSDs to install ports
>> (probably ports were installed by the sysadmin there, and by extension,
>> ports are now always installed there, but that's just a guess).
>
> Maybe. In any case, the practice of using /usr/local for packages
> created from ports is significantly older than the recommendation
> to refrain from using upstream "make install" outside the ports
> framework.
>
> * The FreeBSD ports framework was started by Jordan Hubbard in 1993.
> * The ports framework was ported from FreeBSD to OpenBSD
> by Niklas Hallqvist in 1996.
> * NetBSD pkgsrc was forked from FreeBSD ports by Alistair G. Crooks
> and Hubert Feyrer in 1997.
>
> I failed to quickly find Jordan's original version, but rev. 1.1
> of /usr/ports/infrastructure/mk/bsd.port.mk in OpenBSD (dated Jun 3
> 22:47:10 1996 UTC) already said
>
> LOCALBASE ?= /usr/local
> PREFIX ?= ${LOCALBASE}
>
[...]
>> I had a discussion in NGINX Unit about it, and
>> the decission for now has been: "support prefix=/usr/local for default
>> manual installation through the Makefile, and let BSD users adjust to
>> their preferred path".
>
> That's an *excellent* solution for the task, thanks for doing it
> the right way. By setting PREFIX=/usr/local by default in the
> upstream Makefile, you are minimizing the work for *BSD porters.
>
> The BSD ports frameworks will typically run the upstreak "make install"
> with the variable DESTDIR set to a custom value, for example
>
> DESTDIR=/usr/ports/pobj/groff-1.23.0/fake-amd64
>
> so if the upstream Makefile sets PREFIX=/usr/local ,
> that's perfect, everything gets installed to the right place
> without an intervention by the person doing the porting.
>
> Of course, if the upstream Makefile would use some other PREFIX,
> that would not be a huge obstacle. All we have to do in that case
> is pass the option --prefix=/usr/local to the ./configure script,
> or something equivalent if the software isn't using GNU configure.
>
>> We were concerned that we might get collisions
>> with the BSD port also installing in /usr/local, but that's the least
>> evil (and considering BSD users don't typically run `make install`, it's
>> not so bad).
>
> It's not bad at all. It's perfect.
>
> Of course, if a user wants to install *without* the ports framework,
> they have to provide their own --prefix. But that's not an issue
> because it is easy to do, and installing without a port is discouraged
> anyway.

===

Directory variables should never contain a trailing slash (I've
learned that the hard way, where some things would break
unexpectedly). Especially, make(1) is likely to have problems
when things have double slashes or a trailing slash, since it
treats filenames as text strings. I've removed the trailing slash
from the prefix, and added it to the derivate variables just after
the prefix. pkg-config(1) also expects directory variables to have
no trailing slash.

===

I also removed the code that would set variables as depending on
the prefix if they didn't start with a slash, because that is a
rather non-obvious behavior, and things should not always depend
on prefix, but other dirs such as $(runstatedir), so if we keep
a similar behavior it would be very unreliable. Better keep
variables intact if set, or use the default if unset.

===

Print the real defaults for ./configure --help, rather than the actual
values.

===

I used a subdirectory under the standard /var/lib for NXT_STATE,
instead of a homemade "state" dir that does the same thing.

===

Modified the Makefile to create some dirs that weren't being
created, and also remove those that weren't being removed in
uninstall, probably because someone forgot to add them.

===

Add new options for setting the new variables, and rename some to be
consistent with the standard names. Keep the old ones at configuration
time for compatibility, but mark them as deprecated. Don't keep the old
ones at exec time.

===

A summary of the default config is:

Unit configuration summary:

bin directory: ............. "/usr/local/bin"
sbin directory: ............ "/usr/local/sbin"
lib directory: ............. "/usr/local/lib"
include directory: ......... "/usr/local/include"
man pages directory: ....... "/usr/local/share/man"
modules directory: ......... "/usr/local/lib/unit/modules"
state directory: ........... "/usr/local/var/lib/unit"
tmp directory: ............. "/tmp"

pid file: .................. "/usr/local/var/run/unit/unit.pid"
log file: .................. "/usr/local/var/log/unit/unit.log"

control API socket: ........ "unix:/usr/local/var/run/unit/control.unit.sock"

Link: <https://www.gnu.org/prep/standards/html_node/Directory-Variables.html>
Link: <https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html>
Reviewed-by: Artem Konev <a.konev@f5.com>
Reviewed-by: Andrew Clayton <a.clayton@nginx.com>
Tested-by: Andrew Clayton <a.clayton@nginx.com>
Reviewed-by: Konstantin Pavlov <thresh@nginx.com>
Signed-off-by: Alejandro Colomar <alx@nginx.com>

show more ...


# 2304:ca6c1b6c7ed8 17-Jan-2023 Zhidao HONG

NJS: added the keys API for the request objects.

This commit is to loop through the request objects headers,
arguments, and cookies.


12345678910>>...12