- 29 Dec, 2020 2 commits
-
-
Nils Goroll authored
ref varnish-cache e9c2a488d291b3129838c411cac7312f8801ff1e
-
Nils Goroll authored
Ref varnish-cache 681c11998ec56dc4460a30585210f95a7850ea3b
-
- 17 Nov, 2020 1 commit
-
-
Geoff Simmons authored
-
- 07 Oct, 2020 14 commits
-
-
Nils Goroll authored
Ref varnish-cache f087fe6d37679d8d709cfec85451fde4f68fbb95 Original patch by Poul-Henning Kamp <phk@FreeBSD.org>
-
Nils Goroll authored
and also make bereq.bodybytes account only for the actual bytes in the body, not for the (chunked) overhead. Ref varnish-cache dc37be044f1954b3c7dd497e3e7a5a06c5a9bc5a Original patch by Poul-Henning Kamp <phk@FreeBSD.org>
-
Reza Naghibi authored
Signed-off-by: Nils Goroll <nils.goroll@uplex.de>
-
Nils Goroll authored
Ref varnish-cache 2ab29dc47c1784748e46c60964ca86efa2cdd866
-
Nils Goroll authored
Signed-off-by: Nils Goroll <nils.goroll@uplex.de>
-
-
Dridi Boukelmoune authored
I'm no longer able to time it out under load. Signed-off-by: Nils Goroll <nils.goroll@uplex.de>
-
Nils Goroll authored
-
Nils Goroll authored
Ref varnish-cache ccc1339e6628d6e545b8504d0a230a11f261e930
-
Nils Goroll authored
-
Nils Goroll authored
Ref varnish-cache 78c65ef9cc50f5b449bed1ac040322556c0183c7
-
Nils Goroll authored
Ref varnish-cache a67a9d5606210245dd0c51966698dcd07206c91e
-
Nils Goroll authored
-
Nils Goroll authored
-
- 15 Sep, 2020 1 commit
-
-
Nils Goroll authored
-
- 13 Nov, 2019 2 commits
-
-
Nils Goroll authored
... hopefully, finally The previous code pushing additional data was actually working around other bugs, which _should_ be fixed with 4f9db605 and 6b5c4e45 as shown by permutations.vtc This should avoid running into #3109 on 6.x
-
Nils Goroll authored
Ref fc04ea211f2769cdeb540115ed84ee8908a48cb8
-
- 07 Nov, 2019 5 commits
-
-
Nils Goroll authored
permutations-error.vtc triggers the bad assertion failure fixed in the previous commit
-
Nils Goroll authored
The previous commit went in the right direction, but was not correct. For CHK_ORDER, we must only ever look at type != T_NEXUS and check any T_NEXUS by the criteria originally passed. CHK_ORDER could be stricter still, after a subtree is completed, we could communicate up the stricter CHK_PEND, but I do not want to complicate things further for an assertion.
-
Nils Goroll authored
we do not unpend T_NEXUS nodes, so the following situation is perfectly legal: T_NEXUS ST_CLOSED T_NEXUS T_DATA ST_CLOSED ST_UNPENDING the purpose of the assertion is that, if a node below a nexus is not yet unpended/delivered, the following need to be also, but this is not true for T_NEXUS.
-
Nils Goroll authored
We used to set empty T_DATA nodes to delivered as soon as we encountered them during unpending. While it seemed like a good idea to not spend additional work with nodes which do not contain anything, the tree integrity assertions as well as set_deliver() implicitly assume that - a delivered node cannot follow an undelivered node unter a nexus and - once the last node under a nexus is delivered, all of the nexus is delivered Rather than sacrificing the sensible principle that a tree always is to be delivered top to bottom, left to right, weakening our assertions and possibly introducing new bugs when handling the resulting special cases, we go for the simple, clean option and do away with a special case which will not contribute much to overall performance anyway.
-
Nils Goroll authored
-
- 06 Nov, 2019 1 commit
-
-
Nils Goroll authored
-
- 05 Nov, 2019 10 commits
-
-
Geoff Simmons authored
Avoids starting another process.
-
Geoff Simmons authored
-
Geoff Simmons authored
Avoids the clutter in /tmp.
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
we run into the problem solved by https://github.com/varnishcache/varnish-cache/pull/2942 purely for convenience, we send pass'ed backend requests to ourself (in order not to have to fiddle with the number of requests on servers), yet it can happen that all threads are used up and the herder fails to breed more. So the solution is to ensure that we do not run into any dependency on the herder. this stabilizes permutations.vtc for -j 40 -n 1000
-
Nils Goroll authored
-
Nils Goroll authored
The src argument of vped_include() is owned by the caller vdp_pesi_bytes(), so we need to make a copy on the subrequest's workspace. This is not an issue with varnish-cache ESI because the include is not handed over to a different thread.
-
Nils Goroll authored
we should not emit ReqUnset / ReqHeader if A-E is already correct reflects 6dbfff12dca895534b090ef9283e75f85659fcfa in varnish-cache
-
Nils Goroll authored
to fail earlier for a bug exposed by this test which surfaces as garbled URLs.
-
- 01 Nov, 2019 1 commit
-
-
Nils Goroll authored
-
- 31 Oct, 2019 3 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
in vped_deliver, we used the wrong gzip state pointer for ESI objects, which lead to the pretendgzip filter not being pushed. Also, we should respect the RES_ESI bit to properly handle the case when esi is deactivated on an esi object. (to be tested)
-
Nils Goroll authored
move a block of initializations statements which should run at all levels
-