- 04 Dec, 2023 22 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
It is the VTE's job to deal with alignment now.
-
Dridi Boukelmoune authored
Since the maximum space between fields is 3, it should have been obvious that something was off while inspecting test cases. Before this fix, the fields were aligned, but sometimes the space between fields was too wide and in particular before right-aligned fields.
-
Nils Goroll authored
Fixes vtest error on SunOS gcc4.7.3 -m32: vtim.c: In function 'main': vtim.c:605:2: error: overflow in implicit constant conversion [-Werror=overflow] vtim.c:605:2: error: comparison is always true due to limited range of data type [-Werror=type-limits]
-
Nils Goroll authored
and, in particular, ignore lib/libvarnish/vtim_test too
-
Poul-Henning Kamp authored
-
Nils Goroll authored
The problem with 93974b3f is that the negating option from Makefile.am comes before CFLAGS, which does not disable it for gcc. Tested locally with gcc and clang.
-
Nils Goroll authored
-
Poul-Henning Kamp authored
The ASLR is now so aggresive that it never works.
-
Nils Goroll authored
Ref 01bf0dd2
-
Nils Goroll authored
Ref 63e4f71e
-
Nils Goroll authored
Function: With the fold acl flag enabled (default: disabled, keeping the existing behavior), ACLs are optimized in that subnets contained in other entries are skipped (e.g. if 1.2.3.0/24 is part of the ACL, an entry for 1.2.3.128/25 will not be added) and adjacent entries get folded (e.g. if both 1.2.3.0/25 and 1.2.3.128/25 are added, they will be folded to 1.2.3.0/24). Skip and fold operations on VCL entries are output as warnings during VCL compilation as entries from the VCL are processed in order. Logging under the VCL_acl tag can change with this parameter enabled: Matches on skipped subnet entries are now logged as matches on the respective supernet entry. Matches on folded entries are logged with a shorter netmask which might not be contained in the original ACL as defined in VCL. Such log entries are marked by "fixed: folded". Negated ACL entries are excluded from folds. Implementation: The sort functions are changed such that the previous semantics are preserved: negative return values signify "a < b", positive return values signify "a > b". But additionally the values -2/2 and -3/3 are introduced (and given enums) to signify "contained in supernet" and "directly adjacent to". This allows for mostly unchanged code with vcc_acl_fold disabled. For the "subnet contained in supernet" case, all contained subnets are removed. By sort order, caontained subnets are always to be found left of supernets. For the "fold adjacent" case, the netmask of the entry with the smaller network number is decreased by one and the other entry removed. Because changing the netmask might affect sort order, we reinsert the changed entry.
-
Nils Goroll authored
This is in preparation of a follow-up commit to merge acl entries and detect supersedes from supernets, but these changes are backwards compatible with the previous CMP() if being used as a comparison function for which only negative, zero and positive result are relevant. The A in CMPA() stands for "adjacent". CMPA() returns -3/3 for left of/right of.
-
Nils Goroll authored
Reverts d89674d1 Reinstantiates bbb5db47
-
Dridi Boukelmoune authored
-
Nils Goroll authored
sorry for the glitch
-
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.
-