- 02 Mar, 2020 1 commit
-
-
Dridi Boukelmoune authored
This is the first of a series of mechanical patches made possible by vim macros. This is a first step towards continuing the work initiated in 39e0bc53 and the first observation is that we have some dead weight in the table.
-
- 27 Feb, 2020 1 commit
-
-
Dridi Boukelmoune authored
This was documented following the naming convention in tree, but implemented differently. In order not to change the behavior, only the documentation is updated. Closes #3232
-
- 26 Feb, 2020 7 commits
-
-
Dridi Boukelmoune authored
-
Jordan Christiansen authored
-
Jordan Christiansen authored
-
Nils Goroll authored
fixes #3229
-
Martin Blix Grydeland authored
When doing a pass, we would remove the Age header from the backend, and create a new one based on the time the fetch was initiated. This creates problems when calculating the time to live in downstream caches (browser cache or layered varnishes). With this patch, the RFC_2616_Ttl calculation routine is run also for passes, where the t_origin field of the object is adjusted for an incoming Age header. This makes sure that the Age header generated during delivery is correct. The rest of the Ttl calculation is skipped for passes, including the logging of SLT_TTL "RFC". Fixes: varnishcache/varnish-cache#3221
-
Martin Blix Grydeland authored
One time element function to rule and parse them all.
-
Martin Blix Grydeland authored
Change the return value to unsigned, to match with the expected data type where it is used. Handle very large numbers consistently. Currently it was converting from unsigned long to int, which would throw away the most significant bits. Now overly large integers will be capped at UINT_MAX. Implement the "allow and ignore decimal point" behaviour that the Age header parsing incorporated in rfc2616_time(). This way we will allow a decimal points also in max-age and stale-while-revalidate parsing of Cache-Control directives.
-
- 24 Feb, 2020 7 commits
-
-
Dridi Boukelmoune authored
Better diff with the --word-diff option.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
We have two fallbacks in the absence of a .host_header field in the backend, one of which is systematic. We can build a non .request probe request with a single printf statement. Please note that when the .host field is in the form "$addr $port" we use that as the probe's host header. This behavior is not introduced by this change but ultimately we might want to do something about it and for example capture the first token from hosthdr with a txt.
-
Dridi Boukelmoune authored
In case of failure, I can see which client failed more easily.
-
Nils Goroll authored
-
Poul-Henning Kamp authored
rest of our test-programs are structured.
-
Dridi Boukelmoune authored
-
- 21 Feb, 2020 11 commits
-
-
Guillaume Quintard authored
-
Guillaume Quintard authored
-
Napsty authored
-
Poul-Henning Kamp authored
A lot of this is s/REQ_BODY_/BS_/g, followed by a reduction pass to go from testing on specific status values to attributes of the status value. For instance the req.body caching code does not need to know if how the transport sees this, chunked vs. eof for instance, it just needs to know that there is a body and that we do not know the length of it yet. The transports own the "vocabulary", because internally H1 needs to know the difference between BS_CHUNKED and BS_EOF in order to setup the VFPs.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
This worked only because REQ_BODY_INIT = 0 I hate C enums.
-
- 20 Feb, 2020 6 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
This reverts commit 54e7d45b. However instead of reverting to the previous domain, I picked a different one that I hope will not turn out controversial.
-
Dridi Boukelmoune authored
This is a result of a commit review between 6.2.0 and 6.3.0 and while it should in theory be comprehensive, it is not. The upgrade notes in particular are developer-centric, which may be a sign that none of the changes require attention during an upgrade it could as well be an oversight. There is one item that I identified that should be mentioned in the upgrade guide. I invite @nigoroll to give a shot at the VCL auto state. In the absence of a fair warning, I extended WS_Reserve's grace period. I omitted the -rcvbuf action on purpose, for the same reason why it is not documented in vtc(7) on purpose: it's currently used in conjunction with vmod_debug and we don't ship it. While this is a milestone, I don't consider this work to be done so I didn't remove the notes saying so. We should also probably partially pick 53b4d2f5 on the 6.3 branch.
-
Dridi Boukelmoune authored
-
Klemens Nanni authored
The Keybindings section is the only place mentioning differnt log levels and one might assume that `-1` or `-j` behave the same as the default ncurses interface. The latter however does not show all counters by default as the single action flags do, hence `varnishstat -f '*overload*'` will not show `MAIN.sc_overload` by default, with `-1` however it does. Fix grammar while here.
-
- 19 Feb, 2020 3 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 25 Sep, 2018 1 commit
-
-
Geoff Simmons authored
Restructured so that: * 'Upgrading' is limited to work that has to be done to upgrade from a current deployment to the new version. * 'Changes' is a comprehensive, user-level description of changes and new features. Conflicts: doc/sphinx/whats-new/index.rst
-
- 19 Feb, 2020 3 commits
-
-
Dridi Boukelmoune authored
They are however far from complete, and that's an UNDERSTATEMENT.
-
Poul-Henning Kamp authored
C-spec to understand what the SunOS compiler was whining about. Strictly speaking it has a point, code is different from data is different from const data, so mixing pointers the way we did was not kosher. We probably should have made the identifying argument a uintptr_t instead of const void* to begin with to deal with this.
-
Dridi Boukelmoune authored
This reverts commit 2034138e. We already know that SunCC will complain about those. Alternatively we could use static variables addresses as cookies, but do we need extra symbols?
-