- 20 Jun, 2018 40 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
in our loops.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
is not thread-safe. Switch from random(3) to testable VRND for same reason.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Fixes #2684 Reported by: ernestojpg@github
-
Poul-Henning Kamp authored
Conflicts: bin/varnishd/cache/cache_director.c
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Dag Haavi Finstad authored
Fixes: #2700 Conflicts: bin/varnishd/cache/cache_fetch.c
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Nils Goroll authored
-
Nils Goroll authored
For the purpose of our signal handler (and, in particular, the stack overflow detection heuristic) they are identical. Fixes #2695 (as confirmed by @lkarsten)
-
Poul-Henning Kamp authored
-
Dag Haavi Finstad authored
Ref: #2693
-
Nils Goroll authored
This is the case for the ctx created for director operations as first introduced with 5536f102 Alternatively, we could always set ctx->handling to some location with the same scope as the ctx, but as we are not inside VCL (and just happen to use the same context for simplicity and reusability of VRT/vmod functions), adding specific handling appears to be the cleaner solution. Fixes #2692
-
Dag Haavi Finstad authored
Properly shut down streams where we could not process a req body (e.g. via a failing cache_req_body). The rxthread may be waiting on this stream to consume a DATA frame - let it know before we go away to avoid it being stuck forever.
-
Dag Haavi Finstad authored
-
Dag Haavi Finstad authored
If we have one or more streams set up because of a PRIORITY frame _and_ for some reason a tcp FIN is lost (or a client merely keeps a connection open), this transaction would be stalled indefinitely.
-
Dag Haavi Finstad authored
Avoid failing sessions with pipelined data.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
match syslog-output.
-
Poul-Henning Kamp authored
Submitted by: Frédéric Lécaille <flecaille@haproxy.com> Hacked to pieces by: phk
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Federico G. Schwindt authored
-
Poul-Henning Kamp authored
-
Nils Goroll authored
We already emitted Debug log records for accept failures, but for all practical purposes this is useless for forensics. These counters will point directly to the root cause for the most common issues with sess_fail (accept failures). sess_fail is preserved as an overall counter as it will most likely be already monitored for many installations. Ref #2622 Conflicts: doc/changes.rst
-