- 04 Dec, 2023 6 commits
-
-
Nils Goroll authored
Test case by Martin Blix Grydeland, taken from #4013
-
Dridi Boukelmoune authored
Since Python 3.12 unknown escape sequences trigger a warning.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 22 Nov, 2023 1 commit
-
-
Poul-Henning Kamp authored
-
- 21 Nov, 2023 9 commits
-
-
Dridi Boukelmoune authored
A VCL failure on the client side transitions to vcl_synth, except failures from vcl_synth that lead to minimal errors. The ESI transport is not allowed to reply with minimal responses so this would lead to a panic. On top of that, the vcl_req_reset feature flag emulates `return (fail)` statements when an HTTP/2 client disconnected, resulting in the same panic scenario. For sub-requests, we masquerade the fail transition as a deliver and trade the illegal minimal response for the synthetic response. Fixes #4022
-
Dridi Boukelmoune authored
We have had the ability to reset any parameter to its default value for a while now.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
This is primarily for self-documentation purposes, but also to simplify the bit tweak.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
Better diff with the --ignore-all-space option.
-
Dridi Boukelmoune authored
As opposed to special values. This enables setting "absolute" values atomically: param.set foo none,+bar,+baz
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
The most significant bits of the least significant octet would be omitted when the number of bits is not a multiple of eight.
-
- 20 Nov, 2023 5 commits
-
-
Walid Boudebouda authored
-
Walid Boudebouda authored
Cli command '"help" "help"' was wrongly rejected with error message: "Missing separator between arguments"
-
Walid Boudebouda authored
Output before: PASS: <> with flags 7 as expected. PASS: <foo> with flags 0 as expected. PASS: <foo bar> with flags 0 as expected. PASS: <foo bar> with flags 2 as expected. PASS: <foo,bar> with flags 2 as expected. PASS: < foo bar > with flags 0 as expected. PASS: < foo , bar > with flags 2 as expected. PASS: <foo bar > with flags 2 as expected. PASS: <foo,bar,> with flags 2 as expected. PASS: <foo "bar baz"> with flags 0 as expected. PASS: <foo #bar> with flags 0 as expected. PASS: <foo #bar> with flags 1 as expected. PASS: <foo#bar> with flags 0 as expected. PASS: <foo#bar> with flags 1 as expected. PASS: <\> with flags 4 as expected. PASS: <\x20> with flags 0 as expected. PASS: <foo"bar> with flags 4 as expected. PASS: <"foo""bar"> with flags 4 as expected. Output after: PASS: <> with flags 7 as expected. PASS: <foo> with flags 0 as expected. PASS: <foo bar> with flags 0 as expected. PASS: <foo bar> with flags 2 as expected. PASS: <foo,bar> with flags 2 as expected. PASS: < foo bar > with flags 0 as expected. PASS: < foo , bar > with flags 2 as expected. PASS: <foo bar > with flags 2 as expected. PASS: <foo,bar,> with flags 2 as expected. PASS: <foo "bar baz"> with flags 0 as expected. PASS: <foo #bar> with flags 0 as expected. PASS: <foo #bar> with flags 1 as expected. PASS: <foo#bar> with flags 0 as expected. PASS: <foo#bar> with flags 1 as expected. PASS: <\> with flags 4 as expected. FAIL: <\> with flags 0 as expected. FAIL: <\x> with flags 0 as expected. FAIL: <\x2> with flags 0 as expected. FAIL: <\x2O> with flags 0 as expected. PASS: <\x20> with flags 0 as expected. FAIL: <"foo> with flags 0 as expected. PASS: <foo"bar> with flags 4 as expected. FAIL: <foo"bar> with flags 0 as expected. FAIL: <foo"bar> with flags 0 as expected. PASS: <"foo""bar"> with flags 4 as expected. FAIL: <"foo""bar"> with flags 0 as expected.
-
Walid Boudebouda authored
-
Walid Boudebouda authored
Currently, vav_test always passes make check
-
- 13 Nov, 2023 1 commit
-
-
Dag Haavi Finstad authored
-
- 25 Oct, 2023 2 commits
-
-
Poul-Henning Kamp authored
-
Dridi Boukelmoune authored
We've had contextual min/max/default values in the param.show and param.set output and the manual for a while now.
-
- 24 Oct, 2023 1 commit
-
-
Dridi Boukelmoune authored
-
- 23 Oct, 2023 2 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
- 20 Oct, 2023 1 commit
-
-
Poul-Henning Kamp authored
-
- 18 Oct, 2023 12 commits
-
-
Nils Goroll authored
we can not make the parameter const because API.
-
Nils Goroll authored
-
Nils Goroll authored
(sorry)
-
Nils Goroll authored
as agreed on IRC.
-
Nils Goroll authored
-
Nils Goroll authored
This will allow per-session adjustments and also significantly lower the risk of inconsistent calculations in the rate limit code during parameter changes. Ref #3996
-
Nils Goroll authored
to anchor patches
-
Dridi Boukelmoune authored
Noticed while porting #3998 to the 6.0 branch with a varnishtest more sensitive to timing.
-
Dridi Boukelmoune authored
With #3998 we need to ensure streams are not going to skip vcl_recv if reset faster than reaching this step for the request task. The alternative to prevent the vcl_req_reset feature from interfering is to simply disable it.
-
Dridi Boukelmoune authored
The error check is not performed in a critical section to avoid contention, at the risk of not seeing the error until the next transport poll.
-
Dridi Boukelmoune authored
Once a client is reportedly gone, processing its VCL task(s) is just a waste of resources. The execution of client-facing VCL is intercepted and an artificial return(fail) is returned in that scenario. Thanks to the introduction of the universal return(fail) proper error handling and resource tear down is already in place, which makes this change safe modulus unknown bugs. This adds a circuit breaker anywhere in the client state machine where there is VCL execution. A new Reset time stamp is logged to convey when a task does not complete because the client is gone. This is a good complement to the walk away feature and its original circuit breaker for the waiting list, but this has not been integrated yet. While the request is technically failed, it won't increase the vcl_fail counter, and a new req_reset counter is incremented. This new behavior is guarded by a new vcl_req_reset feature flag, enabled by default. Refs #3835 Refs 61a15cbf Refs e5efc2c8 Refs ba54dc91 Refs 6f50a00f Refs b8816994
-
Dridi Boukelmoune authored
The goal is for top-level transports to report whether the client is still present or not.
-