Warning: file_get_contents(https://raw.githubusercontent.com/Den1xxx/Filemanager/master/languages/ru.json): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /home/familylifersmpc/htdocs/www.familylifersmpc.com/index.php on line 91
.. Copyright (c) 2016 Varnish Software AS SPDX-License-Identifier: BSD-2-Clause See LICENSE file for full text of license .. _whatsnew_upgrading_4_1: %%%%%%%%%%%%%%%%%%%%%%%% Upgrading to Varnish 4.1 %%%%%%%%%%%%%%%%%%%%%%%% Changes to VCL ============== Data type conversion functions now take a fallback ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Data type conversion functions in the std vmod now takes an additional argument *fallback*, which is returned if the conversion does not succeed. Version statement is kept ~~~~~~~~~~~~~~~~~~~~~~~~~ The VCL syntax has not chanced significantly, and as such the Varnish 4.0 version marker is kept for Varnish 4.1. One of the initial lines in a Varnish 4.1 VCL should read:: vcl 4.0; Remote address accessors ~~~~~~~~~~~~~~~~~~~~~~~~ New in 4.1 is the `local.ip` and `remote.ip` representing the (local) TCP connection endpoints. With PROXY listeners the `server.ip` and `client.ip` are set from the PROXY preamble. On normal HTTP listeners the behaviour is unchanged. Management interface ==================== The management interface enabled with ``-M`` previously supported the telnet protocol. Support for telnet control sequences have been retired. Replacement clients like netcat or (preferred) ``varnishadm`` should be used instead. Runtime users and groups ======================== With the new jail support, an additional runtime user (`vcache`) should be used for the Varnish worker child process. Additionally, the ``varnishlog``, ``varnishncsa`` and other Varnish shared log utilities must now be run in a context with `varnish` group membership. Changes to parameters ===================== `vcl_cooldown` is new, and decides how long time a VCL is kept war