Commit 5aaf7cb3 authored by Nils Goroll's avatar Nils Goroll

pick up loose ends of cli_buffer removal

Ref: 6cb21b47
     #2382
parent 4c20c843
varnishtest "Very very big cli_buffer"
# If the cli_buffer is on the stack, setting it very big can crash varnish
server s1 {
rxreq
expect req.url == "/1"
txresp
} -start
varnish v1 -arg "-p cli_buffer=32M" -vcl+backend {
} -start
varnish v1 -cliok "ping"
delay .5
client c1 {
txreq -url /1
rxresp
} -run
......@@ -14,11 +14,13 @@ Varnish Cache Trunk (ongoing)
``req.hash_always_miss`` are now accessible from all of the client
side subs, not just ``vcl_recv{}``
* The ``cli_buffer`` parameter has been removed
================================
Varnish Cache 5.2.0 (2017-09-15)
================================
* The cli_buffer parameter has been deprecated (2382_)
* The ``cli_buffer`` parameter has been deprecated (2382_)
.. _2382: https://github.com/varnishcache/varnish-cache/pull/2382
......
......@@ -285,21 +285,6 @@ PARAM(
/* func */ NULL
)
PARAM(
/* name */ cli_buffer,
/* typ */ bytes_u,
/* min */ "4k",
/* max */ NULL,
/* default */ "8k",
/* units */ "bytes",
/* flags */ 0,
/* s-text */
"DEPRECATED: This parameter is ignored.\n"
"Memory for the CLI command buffer is now dynamically allocated.",
/* l-text */ "",
/* func */ NULL
)
PARAM(
/* name */ cli_limit,
/* typ */ bytes_u,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment