jengelh/varnish
SHA256
1
0
Fork 0
forked from pool/varnish
Code Pull Requests Activity

wrap lines at the very obvious dashed line

Browse Source 
OBS-URL: https://build.opensuse.org/package/show/server:http/varnish?expand=0&rev=119
This commit is contained in:
Jan Engelhardt 2022-10-31 11:22:34 +00:00 committed by Git OBS Bridge
parent e540b355c4
commit bc21f1ddce
1 changed files with 67 additions and 57 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

124
varnish.changes
View File

@ -2,70 +2,80 @@
Sat Oct 29 13:43:46 UTC 2022 - Dirk Müller <dmueller@suse.com> Sat Oct 29 13:43:46 UTC 2022 - Dirk Müller <dmueller@suse.com>
- update to 7.2.0: - update to 7.2.0:
* Functions ``VRT_AddVDP()``, ``VRT_AddVFP()``, ``VRT_RemoveVDP()`` and * Functions ``VRT_AddVDP()``, ``VRT_AddVFP()``,
``VRT_RemoveVFP()`` are deprecated. ``VRT_RemoveVDP()`` and ``VRT_RemoveVFP()`` are deprecated.
* Cookie headers generated by vmod_cookie no longer have a * Cookie headers generated by vmod_cookie no longer have a
spurious trailing semicolon at the end of the string. This spurious trailing semicolon at the end of the string. This
could break VCL relying on the previous incorrect behavior. could break VCL relying on the previous incorrect behavior.
* The ``SessClose`` and ``BackendClose`` reason ``rx_body``, which * The ``SessClose`` and ``BackendClose`` reason ``rx_body``,
previously output ``Failure receiving req.body``, has been rewritten which previously output ``Failure receiving req.body``, has
to ``Failure receiving body``. been rewritten to ``Failure receiving body``.
* Prototypical Varnish Extensions (VEXT). Similar to VMODs, a VEXT is loaded * Prototypical Varnish Extensions (VEXT). Similar to VMODs, a
by the cache process. Unlike VMODs that have the combined lifetime of all VEXT is loaded by the cache process. Unlike VMODs that have
the VCLs that reference them, a VEXT has the lifetime of the cache process the combined lifetime of all the VCLs that reference them, a
itself. There are no built-in extensions so far. VEXT has the lifetime of the cache process itself. There are
* Duration parameters can optionally take a unit, with the same syntax as no built-in extensions so far.
duration units in VCL. * Duration parameters can optionally take a unit, with the same
* Calls to ``VRT_CacheReqBody()`` and ``std.cache_req_body`` from outside syntax as duration units in VCL.
client vcl subs now fail properly instead of triggering an * Calls to ``VRT_CacheReqBody()`` and ``std.cache_req_body``
assertion failure. from outside client vcl subs now fail properly instead of
* New "B" string for the package branch in ``VCS_String()``. For the 7.2.0 triggering an assertion failure.
version, it would yield the 7.2 branch. * New "B" string for the package branch in ``VCS_String()``.
* The new ``vcc_feature`` bits parameter replaces previous ``vcc_*`` boolean For the 7.2.0 version, it would yield the 7.2 branch.
parameters. The latter still exist as deprecated aliases. * The new ``vcc_feature`` bits parameter replaces previous
* The ``-k`` option from ``varnishlog`` is now supported by ``varnishncsa``. ``vcc_*`` boolean parameters. The latter still exist as
* New functions ``std.now()`` and ``std.timed_call()`` in vmod_std. deprecated aliases.
* The ``-k`` option from ``varnishlog`` is now supported by
``varnishncsa``.
* New functions ``std.now()`` and ``std.timed_call()`` in
vmod_std.
* New ``MAIN.shm_bytes`` counter. * New ``MAIN.shm_bytes`` counter.
* A ``req.http.via`` header is set before entering ``vcl_recv``. Via headers * A ``req.http.via`` header is set before entering
are generated using the ``server.identity`` value. It defaults to the host ``vcl_recv``. Via headers are generated using the
name and can be turned into a pseudonym with the ``varnishd -i`` option. ``server.identity`` value. It defaults to the host name and
Via headers are appended in both directions, to work with other hops that can be turned into a pseudonym with the ``varnishd -i``
may advertise themselves. option. Via headers are appended in both directions, to work
* A ``resp.http.via`` header is no longer overwritten by varnish, but with other hops that may advertise themselves.
rather appended to. * A ``resp.http.via`` header is no longer overwritten by
* The ``server.identity`` syntax is now limited to a "token" as defined in varnish, but rather appended to.
the HTTP grammar to be suitable for Via headers. * The ``server.identity`` syntax is now limited to a "token" as
* In ``varnishtest`` a Varnish instance will use its VTC instance name as its defined in the HTTP grammar to be suitable for Via headers.
instance name (``varnishd -i``) by default for predictable Via headers in * In ``varnishtest`` a Varnish instance will use its VTC
test cases. instance name as its instance name (``varnishd -i``) by
default for predictable Via headers in test cases.
* VMOD and VEXT authors can use functions from ``vnum.h``. * VMOD and VEXT authors can use functions from ``vnum.h``.
* Do not filter pseudo-headers as regular headers (VSV00009_ / 3830_). * Do not filter pseudo-headers as regular headers.
* The termination rules for ``WRK_BgThread()`` were relaxed to allow VMODs to * The termination rules for ``WRK_BgThread()`` were relaxed to
use it. allow VMODs to use it.
* ``(struct worker).handling`` has been moved to the newly introduced * ``(struct worker).handling`` has been moved to the newly
``struct wrk_vpi`` and replaced by a pointer to it, as well as introduced ``struct wrk_vpi`` and replaced by a pointer to
``(struct vrt_ctx).handling`` has been replaced by that pointer. it, as well as ``(struct vrt_ctx).handling`` has been
``struct wrk_vpi`` is for state at the interface between VRT and VGC replaced by that pointer. ``struct wrk_vpi`` is for state at
and, in particular, is not const as ``struct vrt_ctx`` aka the interface between VRT and VGC and, in particular, is not
``VRT_CTX``. const as ``struct vrt_ctx`` aka ``VRT_CTX``.
* Panics now contain information about VCL source files and lines. * Panics now contain information about VCL source files and
* The ``Begin`` log record has a 4th field for subtasks like ESI sub-requests. lines.
* The ``-E`` option for log utilities now works as documented, with any type * The ``Begin`` log record has a 4th field for subtasks like
of sub-task based on the ``Begin[4]`` field. This covers ESI like before, ESI sub-requests.
and sub-tasks spawned by VMODs (provided that they log the new field). * The ``-E`` option for log utilities now works as documented,
with any type of sub-task based on the ``Begin[4]`` field.
This covers ESI like before, and sub-tasks spawned by VMODs
(provided that they log the new field).
* No more ``req.http.transfer-encoding`` for ESI sub-requests. * No more ``req.http.transfer-encoding`` for ESI sub-requests.
* The thread pool reserve is now limited to tasks that can be queued. A * The thread pool reserve is now limited to tasks that can be
backend background fetch is no longer eligible for queueing. It would queued. A backend background fetch is no longer eligible for
otherwise slow a grace hit down significantly when thread pools are queueing. It would otherwise slow a grace hit down
saturated. significantly when thread pools are saturated.
* The unused ``fetch_no_thread`` counter was renamed to ``bgfetch_no_thread`` * The unused ``fetch_no_thread`` counter was renamed to
because regular backend fetch tasks are always scheduled. ``bgfetch_no_thread`` because regular backend fetch tasks are
always scheduled.
* The macros ``FEATURE()``, ``EXPERIMENT()``, ``DO_DEBUG()``, * The macros ``FEATURE()``, ``EXPERIMENT()``, ``DO_DEBUG()``,
``MGT_FEATURE()``, ``MGT_EXPERIMENT()``, ``MGT_DO_DEBUG()`` and ``MGT_FEATURE()``, ``MGT_EXPERIMENT()``, ``MGT_DO_DEBUG()``
``MGT_VCC_FEATURE()`` now return a boolean value (``0`` or ``1``) and ``MGT_VCC_FEATURE()`` now return a boolean value (``0``
instead of the (private) flag value. or ``1``) instead of the (private) flag value.
* A regression in the transport code led MAIN.client_req to be incremented * A regression in the transport code led MAIN.client_req to be
for requests coming back from the waiting list, it was fixed. incremented for requests coming back from the waiting list,
it was fixed.
------------------------------------------------------------------- -------------------------------------------------------------------
Wed Sep 21 08:10:13 UTC 2022 - Bernhard Wiedemann <bwiedemann@suse.com> Wed Sep 21 08:10:13 UTC 2022 - Bernhard Wiedemann <bwiedemann@suse.com>