Merge branch 'main' into patch-1

JTorreG · web-flow · commit 9995e19de381 · 2024-05-23T11:38:33.000+01:00
diff --git a/source/CHANGES.txt b/source/CHANGES.txt
@@ -1,4 +1,66 @@
 
+Changes with Unit 1.32.1                                         26 Mar 2024
+
+    *) Bugfix: NJS variables in templates may have incorrect values due to
+       improper caching.
+
+    *) Bugfix: Wasm application process hangs after receiving restart signal
+       from the control.
+
+
+Changes with Unit 1.32.0                                         27 Feb 2024
+
+    *) Feature: WebAssembly Components using WASI interfaces defined in
+       wasi:http/proxy@0.2.0.
+
+    *) Feature: conditional access logging.
+
+    *) Feature: NJS variables access.
+
+    *) Feature: $request_id variable contains a string that is formed using
+       random data and can be used as a unique request identifier.
+
+    *) Feature: options to set control socket permissions.
+
+    *) Feature: Ruby arrays in response headers, improving compatibility
+       with Rack v3.0.
+
+    *) Feature: Python bytearray response bodies for ASGI applications.
+
+    *) Bugfix: router could crash while sending large files. Thanks to
+       rustedsword.
+
+    *) Bugfix: serving static files from a network filesystem could lead to
+       error.
+
+    *) Bugfix: "uidmap" and "gidmap" isolation options validation.
+
+    *) Bugfix: abstract UNIX socket name could be corrupted during
+       configuration validation. Thanks to Alejandro Colomar.
+
+    *) Bugfix: HTTP header field value encoding could be misinterpreted in
+       Python module.
+
+    *) Bugfix: Node.js http.createServer() accepts and ignores the "options"
+       argument, improving compatibility with strapi applications, among
+       others.
+
+    *) Bugfix: ServerRequest.flushHeaders() implemented in Node.js module to
+       make it compatible with Next.js.
+
+    *) Bugfix: ServerRequest.httpVersion variable format in Node.js module.
+
+    *) Bugfix: Node.js module handles standard library imports prefixed with
+       "node:", making it possible to run newer Nuxt applications, among
+       others.
+
+    *) Bugfix: Node.js tarball location changed to avoid build/install
+       errors.
+
+    *) Bugfix: Go module sets environment variables necessary for building
+       on macOS/arm64 systems.
+
+
 Changes with Unit 1.31.1                                         19 Oct 2023
 
     *) Feature: allow to set the HTTP response status in Wasm module.
diff --git a/source/community.rst b/source/community.rst
@@ -23,7 +23,7 @@ Contribution
 ************
 
 NGINX Unit is released under the
-`Apache 2.0 license <https://hg.nginx.org/unit/file/tip/LICENSE>`_;
+`Apache 2.0 license <https://github.com/nginx/unit/blob/master/LICENSE>`_;
 we maintain GitHub
 `repos <https://github.com/nginx>`_.
 
diff --git a/source/conf.py b/source/conf.py
@@ -5,8 +5,8 @@
 project = 'NGINX Unit'
 author = 'NGINX, Inc.'
 copyright = '2017-2024'
-version = '1.32.0'
-release_date = 'Feb 27, 2024'
+version = '1.32.1'
+release_date = 'Mar 26, 2024'
 release = version
 needs_sphinx = '6.2'
 
diff --git a/source/configuration.rst b/source/configuration.rst
@@ -5025,31 +5025,21 @@ you have:
 .. list-table::
    :header-rows: 1
 
-    * - Option
-      - Description
-
-    * - **script** (required)
-      - String;
-         rack script pathname,
-         including the **.ru** extension,
-         for instance:
-         **/www/rubyapp/script.ru**.
+   * - Option
+     - Description
 
-    * - **hooks**
-      - String;
-         pathname of the **.rb** file
-         setting the event hooks
-         invoked during the app's lifecycle.
+   * - **script** (required)
+     - String; rack script pathname, including the **.ru** extension,
+       for instance: **/www/rubyapp/script.ru**.
 
-    * - **threads**
-      - Integer;
-         number of worker threads
-         per :ref:`app process <sec-processes>`.
-         When started,
-         each app process creates this number of threads
-         to handle requests.
+   * - **hooks**
+     - String; pathname of the **.rb** file setting the event hooks invoked
+       during the app's lifecycle.
 
-         The default is **1**.
+   * - **threads**
+     - Integer; number of worker threads per
+       :ref:`app process <sec-processes>`. When started, each app process
+       creates this number of threads to handle requests. The default is **1**.
 
 Example:
 
@@ -5637,7 +5627,7 @@ recorded. The **if** option supports a string and JavaScript code.
 If its value is empty, 0, false, null, or undefined, the logs will not be
 recorded. And the '!' as a prefix inverses the condition.
 
-Example without NJS:
+Example without njs:
 
 .. code-block:: json
 
@@ -5663,7 +5653,7 @@ We can add ! to inverse the condition.
 
 Now, all requests without a session cookie will be logged.
 
-Example with NJS and the use of a template literal:
+Example with njs and the use of a template literal:
 
 .. code-block:: json
 
diff --git a/source/exts/github.py b/source/exts/github.py
@@ -9,7 +9,7 @@
 layout.html:
     {% if edit_on_github_url %}
         <div class="nxt_github_link">
-            <a href="{{ edit_on_github_url }}"><div></div>Improve this page</a>
+            <a href="{{ edit_on_github_url }}"><div></div>Edit this page</a>
         </div>
     {% endif %}
 """
diff --git a/source/exts/nxt.py b/source/exts/nxt.py
@@ -440,20 +440,20 @@ def depart_nxt_tabs(self, node: Element) -> None:
 
     def __write_news_entry(self, e: List[dict], prefix: str = "") -> None:
         date = datetime.fromisoformat(e["date"]).strftime("%B %-d, %Y")
-        self.body.append(
-            f"""
-            <div class=nxt_news_item>
-             <h2>
-                 {e['title']}
-                 <a class=headerlink href={prefix + e['anchor']}
-                     title="Permalink to this headline">§</a>
-             </h2>
-             <p class=nxt_news_authordate>
-                 {e['author']}&nbsp;on&nbsp;{date}
-             </p>
-             <p>{e['description']}</p>"""
-        )
         if "relurl" in e:
+            self.body.append(
+                f"""
+                <div class=nxt_news_item>
+                <h2>
+                    <a href={e["relurl"]}>{e['title']}</a>
+                    <a class=headerlink href={prefix + e['anchor']}
+                        title="Permalink to this headline">§</a>
+                </h2>
+                <p class=nxt_news_authordate>
+                    {e['author']}&nbsp;on&nbsp;{date}
+                </p>
+                <p>{e['description']}</p>"""
+            )
             domain = urlparse(e["relurl"]).netloc
             if domain.startswith("www."):
                 domain = domain[4:]
diff --git a/source/go b/source/go
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html>
 <head>
-<meta name="go-import" content="unit.nginx.org hg https://hg.nginx.org/unit" />
+<meta name="go-import" content="unit.nginx.org git https://github.com/nginx/unit" />
 <meta http-equiv="refresh" content="0; url=/configuration/#modifying-go-sources" />
 </head>
 <body>
diff --git a/source/howto/docker.rst b/source/howto/docker.rst
@@ -424,7 +424,7 @@ Dockerfile layer:
 
 .. subs-code-block:: docker
 
-   FROM nginx/unit:|version|-minimal
+   FROM unit:|version|-minimal
 
    CMD ["unitd-debug","--no-daemon","--control","unix:/var/run/control.unit.sock"]
 
@@ -434,7 +434,7 @@ executable with its debug version.  Use Unit's :ref:`command-line options
 
 .. subs-code-block:: docker
 
-   FROM nginx/unit:|version|-minimal
+   FROM unit:|version|-minimal
 
    CMD ["unitd","--no-daemon","--control","0.0.0.0:8080"]
 
diff --git a/source/howto/modules.rst b/source/howto/modules.rst
@@ -115,7 +115,7 @@ adjust the command samples as needed to fit your scenario.
    For details of building Unit language modules, see the source code
    :ref:`howto <source-modules>`; it also describes building
    :doc:`Unit <source>` itself.  For more packaging examples, see our package
-   `sources <https://hg.nginx.org/unit/file/tip/pkg/>`_.
+   `sources <https://github.com/nginx/unit/tree/master/pkg>`_.
 
 ..
    Legacy anchors to preserve existing external links.
diff --git a/source/installation.rst b/source/installation.rst
@@ -1724,7 +1724,7 @@ make sure to update the module as well:
 
    .. code-block:: console
 
-      $ hg clone https://hg.nginx.org/unit
+      $ git clone https://github.com/nginx/unit
       $ cd unit
       $ pwd
             :nxt_hint:`/home/user/unit <Note the path to the source code>`
diff --git a/source/news/2018/unit-1.4-released.rst b/source/news/2018/unit-1.4-released.rst
@@ -59,7 +59,8 @@ routing, and serving of static media assets.
 
 Please also welcome Artem Konev, who joined our team as a technical writer.  He
 has already started improving documentation on the website and updated it with
-the configuration options currently available: https://hg.nginx.org/unit-docs/
+the configuration options currently available:
+https://github.com/nginx/unit-docs/
 
 Of course, the website still leaves much to be desired, so Artem will strive to
 provide industry-grade documentation for Unit.  You are welcome to join this
diff --git a/source/news/2023/index.rst b/source/news/2023/index.rst
@@ -53,7 +53,7 @@ News archive for the year 2023.
 
 .. nxt_news_entry::
    :author: Unit Team
-   :description: Version 1.30.0 adds URI rewrites, expands NJS integration and
+   :description: Version 1.30.0 adds URI rewrites, expands njs integration and
                  logging capabilities, and introduces an OpenAPI specification.
    :email: unit-owner@nginx.org
    :title: Unit 1.30.0 Released
@@ -63,7 +63,7 @@ News archive for the year 2023.
 .. nxt_news_entry::
    :author: Unit Team
    :description: Version 1.29.1 addresses assorted bugs in PHP and Python app
-                 handling, NJS integration, and WebSockets.
+                 handling, njs integration, and WebSockets.
    :email: unit-owner@nginx.org
    :title: Unit 1.29.1 Released
    :date: 2023-02-28
diff --git a/source/news/2024/index.rst b/source/news/2024/index.rst
@@ -4,17 +4,25 @@ News of 2024
 
 News archive for the year 2024.
 
+.. nxt_news_entry::
+   :author: Unit Team
+   :description: Version 1.32.1 is a maintenance release that fixes bugs in the new WebAssembly Language Module and in our njs implementation.
+   :email: unit-owner@nginx.org
+   :title: Unit 1.32.1 Released
+   :url: news/2024/unit-1.32.1-released
+   :date: 2024-03-26
+
 .. nxt_news_entry::
    :author: Timo Stark
-   :description: Building Wasm Components using Feryon's Spin SDK for Rust
+   :description: Building Wasm Components using Fermyon's Spin SDK for Rust
                  and run them on NGINX Unit.
    :email: unit-owner@nginx.org
    :title: Wasm Components: Working with the Spin SDK for Rust
    :url: news/2024/fermyon-spin-rust-sdk
    :date: 2024-03-13
-   
+
 .. nxt_news_entry::
-   :author: Timo Stark 
+   :author: Timo Stark
    :description: Part 2 of our Wasm Component Model blog series. In this Blog post you will learn
                  how to build a Rust based Wasm Component and run it on NGINX Unit.
    :email: unit-owner@nginx.org
diff --git a/source/news/2024/unit-1.32.0-released.rst b/source/news/2024/unit-1.32.0-released.rst
@@ -15,7 +15,7 @@ the old **unit-wasm** module deprecated now.
 
 Additionally, we have added the following features:
 
-- Enhanced the :doc:`NJS (NGINX JavaScript) experience <../../scripting>` by making all Unit variables
+- Enhanced the :doc:`njs (NGINX JavaScript) experience <../../scripting>` by making all Unit variables
   accessible from JavaScript
 
 - Added support for
diff --git a/source/news/2024/unit-1.32.1-released.rst b/source/news/2024/unit-1.32.1-released.rst
@@ -0,0 +1,52 @@
+:orphan:
+
+####################
+Unit 1.32.1 Released
+####################
+
+NGINX Unit 1.32.1 is a maintenance release that fixes bugs in the new WebAssembly Language Module and in our njs implementation.
+
+===============
+Resolved issues
+===============
+
+This release fixes the following issues:
+
+**************************************************************
+Applications of type `wasm-wasi-component` can't be restarted
+**************************************************************
+
+Applications deployed as `wasm-wasi-components` can't be restarted using the `restart` endpoint.
+
+After deploying a new Wasm Component binary to disk, the restart will trigger a reload of the component in Unit without restarting the server.
+
+As restarts will work independently of the application type, the behavior shipped with **1.32.0** was not right. It has been fixed in this release.
+
+
+************************************************************
+Unit-variables in NGINX JavaScript are constantly cached
+************************************************************
+
+In **1.32.0** we added the possibility to access all Unit variables form inside njs.
+
+As reported in GitHub issue `#1169 <https://github.com/nginx/unit/issues/1169>`__ the variables were cached and would hold the wrong value, which is not how this feature should work. With version 1.32.1, we have fixed this issue.
+
+
+==============
+Full Changelog
+==============
+
+.. code-block:: none
+
+    Changes with Unit 1.32.1                                         26 Mar 2024
+
+        *) Bugfix: NJS variables in templates may have incorrect values due to
+           improper caching.
+
+        *) Bugfix: Wasm application process hangs after receiving restart signal
+           from the control.
+
+
+
+For a full list of changes and bugfixes,
+please see the `changelog <../../../CHANGES.txt>`__.
diff --git a/source/news/2024/wasm-component-model-part-2.rst b/source/news/2024/wasm-component-model-part-2.rst
diff --git a/source/theme/layout.html b/source/theme/layout.html
diff --git a/source/theme/static/style.css b/source/theme/static/style.css
