- 05 May, 2014 13 commits
-
-
Joshua Bussdieker authored
-
Lasse Karstensen authored
Update changelog
-
Poul-Henning Kamp authored
Submitted by: github::brianjarita
-
Lasse Karstensen authored
As discussed on bugwash today. Lowering the bar may help us improve the documentation.
-
Dag Haavi Finstad authored
-
Nils Goroll authored
-
Martin Blix Grydeland authored
The pool herder didn't signal the thread when decimating the flock, causing the thread to be leaked. Spotted by: xcir Fixes: #1490 Also close a couple of other races: When pthread_cond_timedwait returns ETIMEDOUT, the predicate (wrk->task.func == NULL) could still have changed while reacquiring the mutex. If so, the signal would've been lost and the thread leaked. Changed the idle wait loop in Pool_Work_Thread() to always check the predicate before resuming the cond_wait. The update of the predicate (wrk->task.func) from e.g. Pool_Task() is done without holding the mutex. This opens a race on the predicate, and the possibility of the worker going back on cond_wait loosing the signal. Changed to update the predicate while holding the mutex.
-
Poul-Henning Kamp authored
Spotted by: Coverity
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Spotted by: Coverity
-
Poul-Henning Kamp authored
-
Per Buer authored
-
Poul-Henning Kamp authored
In 4.x we changed obj.hits to be read-only, and to count all variants under the same hash-key (= same objhdr). Since we cannot trivially tell if a ban hits all Vary: values or just some of them, there is no sane heuristic to fiddle obj.hits on bans that would Do The Right Thing. Fixes #1492
-
- 02 May, 2014 1 commit
-
-
Lasse Karstensen authored
Also remove the libvarnishapi "workaround" we put in place earlier. Found by: Ingvar Hagelund Fixes: #1484
-
- 30 Apr, 2014 1 commit
-
-
Martin Blix Grydeland authored
Fixes: #1489 Spotted by: xcir
-
- 28 Apr, 2014 2 commits
-
-
Federico G. Schwindt authored
Update board members, URLs, spelling and fmt(1).
-
Martin Blix Grydeland authored
The disembarking thread would clear the req->wrk pointer in CNT_Request. The req could have already been rescheduled on another worker at this point, causing the req->wrk to be cleared while processing. Change back to not clearing the pointer for REQ_FSM_DISEMBARK (it's already been done under mutex in HSH_Lookup anyways). Fixes: #1488
-
- 27 Apr, 2014 1 commit
-
-
Federico G. Schwindt authored
-
- 25 Apr, 2014 3 commits
-
-
Martin Blix Grydeland authored
backend IMS. When revalidating using backend IMS, copy the status code, status code, status string and response message from the original object into the new revalidated object. This makes sure that none of the 304 message fields gets applied to the new revalidated object. Fixes: #1485
-
Martin Blix Grydeland authored
The Age reported on response objects is calculated from the last request timestamp taken. For a cache hit that hasn't been on a waitinglist, that will be the Start timestamp. This opens a race where the requests' last timestamp could be before the objects t_origin. Truncate the Age to zero rather than assert in that case. Fixes: #1486
-
Poul-Henning Kamp authored
-
- 24 Apr, 2014 1 commit
-
-
Tollef Fog Heen authored
If one runs configure with --without-rst2man or no rst2man is found, the value is "no", not an empty string. Handle this correctly in configure. Fixes: #1473
-
- 23 Apr, 2014 1 commit
-
-
Dag Haavi Finstad authored
-
- 22 Apr, 2014 3 commits
-
-
Per Buer authored
-
Poul-Henning Kamp authored
specific user and/or group may execute it. Varnish never inherited the groups of the user that has been specified by "-u". initgroups() will make sure that varnish gets all supplementary groups. Submitted by: Christian Ruppert Fixes #1482
-
Poul-Henning Kamp authored
who made them with Coccinelle. Thanks!
-
- 21 Apr, 2014 1 commit
-
-
Andreas Plesner authored
Fixes #1480
-
- 17 Apr, 2014 1 commit
-
-
Matt Robenolt authored
-
- 16 Apr, 2014 1 commit
-
-
Federico G. Schwindt authored
Pointed out by dharrigan in #varnish.
-
- 14 Apr, 2014 5 commits
-
-
Martin Blix Grydeland authored
-
Martin Blix Grydeland authored
-
Martin Blix Grydeland authored
Before, the origin time for the objects was defined as the time we received the full request from the client that initiated the fetch. Now we use the time we received the response headers from the backend.
-
Martin Blix Grydeland authored
The EXP_Touch and the Age header will be based off the last timestamp taken. This can be slightly inaccurate, but saves us from having to do another timestamp for them. Fixes: #1475
-
Martin Blix Grydeland authored
backend. Set it on the object if missing. Previously we would add an explicit Date header on each response with the time and date of the response, overwriting any Date header on the object that came from the backend. Now we will add a Date header if the backend didn't supply one just before vcl_backend_response() is run, and not add any Date headers for the replies. This change means Date headers sent by Varnish is approximately the time and date this object was generated by the backend, and not the current date and time.
-
- 12 Apr, 2014 2 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 11 Apr, 2014 4 commits
-
-
Poul-Henning Kamp authored
-
Federico G. Schwindt authored
While here fmt(1) the text.
-
Federico G. Schwindt authored
-
Andreas Plesner authored
-