- 24 Apr, 2023 11 commits
-
-
Nils Goroll authored
to facilitate custom filter parametrization
-
Dag Haavi Finstad authored
This requirement was dropped in the updated rfc 9113. Fixes: #3911
-
Walid Boudebouda authored
-
Walid Boudebouda authored
-
Walid Boudebouda authored
Both $Functions call VRT_purge which fails if not called from vcl_hit or vcl_miss
-
Walid Boudebouda authored
Since all functions of vmod_proxy use ctx->req, they should then be restricted to client context only
-
Walid Boudebouda authored
-
Walid Boudebouda authored
-
Walid Boudebouda authored
This commit implements the $Restrict feature described in https://github.com/varnishcache/varnish-cache/wiki/VIP4%3A-Restrict-VMOD-function-call-sites it offers the ability to restrict vmod functions and methods scope so that they can only be called from limited VCL call sites
-
Shohei Tanaka authored
-
- 23 Apr, 2023 5 commits
-
-
Nils Goroll authored
the 32bit vtesters did not hit all error paths
-
Nils Goroll authored
also cover the case without a response body and check that we actually hit the error conditions which we intent to test.
-
Nils Goroll authored
to keep down the number of ephemeral TCP ports used.
-
Nils Goroll authored
Preparing to extend the test with the default vtc log buffer size.
-
Nils Goroll authored
Currently the only possible cause is a workspace_client overflow, but should v1d ever gain an init callback, that could change. At any rate the cause is never a workspace_thread overflow.
-
- 19 Apr, 2023 2 commits
-
-
Walid Boudebouda authored
-
Walid Boudebouda authored
-
- 18 Apr, 2023 2 commits
-
-
Dridi Boukelmoune authored
We only log a Storage record when we successfully create an object, but there may be no clue regarding which storage backend failed to allocate. We can infer from stevedore VSCs where allocation failures happened, but knowing from a VCL transaction which one failed will give a definitive answer. This is logged as an Error record, and the existing FetchError record from VFPs ("Could not get storage") is left alone.
-
Dridi Boukelmoune authored
When mgt sends a command to the cache process, whether it is a period ping or an actual operation, it must complete within cli_timeout. When the cache fails to meet this requirement, mgt sends a SIGQUIT signal to the cache process. As a result the cache process MAY dump a core file for post-mortem analysis. When the core file is missing we are left to our own devices. To mitigate this, a new signal handler is added for SIGQUIT, but since we can't (or don't even try to) guarantee delivery on the CLI thread, we make a last-ditch effort to forward SIGQUIT signals to properly panic from the CLI thread. With a regular panic we may get both a panic report and a core dump. I didn't add test coverage for this, since we try to avoid intentional core dumps in test cases with the `no_coredump` feature flag that turns SIGQUIT into a SIGKILL signal.
-
- 14 Apr, 2023 3 commits
-
-
Dridi Boukelmoune authored
Refs #3897
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
This reverts commit 1a9beb31. See discussion from #3897.
-
- 12 Apr, 2023 2 commits
-
-
Poul-Henning Kamp authored
gets remapped a different place. (This would be horribly slow to run in production.)
-
Nils Goroll authored
This is useful to test extensions with otherwise unaltered varnish test cases, for example: VTEST_VARNISHD_ADD_ARGS='-E/tmp/lib/varnish/vmods/libvmod_slash.so -sfellow=fellow,${tmpdir}/fellow.stv,100MB,1MB,64KB -sTransient=fellow,${tmpdir}/transient.stv,100MB,1MB,64KB' ./varnishtest -i ... These arguments are added and this injection method does not achieve its goal in all cases (e.g. for the example it breaks when other stevedore definitions conflict), but it still reduces the cases requiring manual intervention substantially.
-
- 11 Apr, 2023 3 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 09 Apr, 2023 1 commit
-
-
Poul-Henning Kamp authored
-
- 08 Apr, 2023 3 commits
-
-
Poul-Henning Kamp authored
-
Nils Goroll authored
... that there is no v1l open already for the worker. This enables the assertion also for use on the backend side.
-
Nils Goroll authored
When we fail a HTTP1 connection via v1d_error(), we write directly to the file descriptor and thus should assert that there is no V1L (line handler) open. We had this check only for two out of the four early returns from V1D_Deliver().
-
- 07 Apr, 2023 3 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 06 Apr, 2023 4 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 04 Apr, 2023 1 commit
-
-
Nils Goroll authored
Dridi/dag tell me that changes.rst is not ready for it. This reverts commit 10633ae0.
-