varnish
No description set
- Devel package for openSUSE:Factory
-
3
derived packages
- Developed at SCM
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout server:http/varnish && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
uninit.patch | 0000001007 1007 Bytes | |
varnish-5.1.2-add-fallthrough-comments.patch | 0000005658 5.53 KB | |
varnish-7.2.0.tgz | 0004018697 3.83 MB | |
varnish.changes | 0000027939 27.3 KB | |
varnish.logrotate | 0000000190 190 Bytes | |
varnish.service | 0000000714 714 Bytes | |
varnish.spec | 0000006115 5.97 KB | |
varnish.sysconfig | 0000000763 763 Bytes | |
varnish_reload_vcl | 0000000308 308 Bytes | |
varnishlog.service | 0000000661 661 Bytes |
Revision 117 (latest revision is 135)
Jan Engelhardt (jengelh)
accepted
request 1032206
from
Dirk Mueller (dirkmueller)
(revision 117)
- update to 7.2.0: * Functions ``VRT_AddVDP()``, ``VRT_AddVFP()``, ``VRT_RemoveVDP()`` and ``VRT_RemoveVFP()`` are deprecated. * Cookie headers generated by vmod_cookie no longer have a spurious trailing semi-colon (``';'``) at the end of the string. This could break VCL relying on the previous incorrect behavior. * The ``SessClose`` and ``BackendClose`` reason ``rx_body``, which previously output ``Failure receiving req.body``, has been rewritten to ``Failure receiving body``. * Prototypical Varnish Extensions (VEXT). Similar to VMODs, a VEXT is loaded by the cache process. Unlike VMODs that have the combined lifetime of all the VCLs that reference them, a VEXT has the lifetime of the cache process itself. There are no built-in extensions so far. * The VCC (compilation) process no longer loads VMODs with ``dlopen(3)`` to collect their metadata. * Stevedore initialization via the ``.init()`` callback has been moved to the worker process. * The parameter ``tcp_keepalive_time`` is supported on MacOS. * Duration parameters can optionally take a unit, with the same syntax as duration units in VCL. Example: ``param.set default_grace 1h``. * Calls to ``VRT_CacheReqBody()`` and ``std.cache_req_body`` from outside client vcl subs now fail properly instead of triggering an assertion failure (3846_). * New ``"B"`` string for the package branch in ``VCS_String()``. For the 7.2.0 version, it would yield the 7.2 branch. * The Varnish version and branch are available in ``varnishtest`` through the ``${pkg_version}`` and ``${pkg_branch}`` macros. * New ``${topsrc}`` macro in ``varnishtest -i`` mode. * New ``process pNAME -match-text`` command in ``varnishtest`` to expect text matching a regular expression on screen.
Comments 1
This probably should be bumped to 6.3.2: http://varnish-cache.org/security/VSV00005.html#vsv00005