This commit was guided by the cocci patch below, but lines to change
were manually selected.

Motivated by #3864

	--- 8< ---

@@
expression path;
@@

- *path == '/'
+ VUS_is(path)

@@
expression path;
@@

- *path != '/'
+ ! VUS_is(path)

we only forwarded the result from a single read(), which might have
missed information on the actual error.

space for larger XIDs.  Add a version field.

We had three call sites, one with and two without size checking.

Other improvements:

- zero (struct sockaddr_un).sun_path
- set errno if the path argument does not fit

Motivated by: #3863

to anchor patches

As far as I can see, this is only used in the vim->n_ stats, which are,
apparently, not used anywhere.

Check for correct handling of missing pseudo-headers, and invalid
characters.
Signed-off-by: Asad Sajjad Ahmed <asadsa@varnish-software.com>

We should apply the same restrictions on the list of allowed characters inside
H/2 pseudo-headers as we do for H/1. This error is translated into the
headers we send to a backend over H/1.

Failure to do so could permit various exploits against a backend not handling
malformed H/1 requests.
Signed-off-by: Asad Sajjad Ahmed <asadsa@varnish-software.com>

This expands the perfect hash lookup table to be able to match any entry
in the list of well-known headers from tbl/http_headers.h.

Previously only the headers that had a non-zero filter flag section was
kept in the fast match table.

Fixes: VSV00010

We do not need to periodically check the conditions in
obj_extend_condwait() if we ensure that HSH_Cancel() triggers a
wakeup.

Readers on private objects need to ensure they call HSH_Cancel() if
they abort the read, so this is consistent with our requirements.

While we could add a seperate function to the object API for the sole
purpose of signaling a cancel, HSH_Cancel() already calls
ObjWaitState() to syncronize with the backend thread, so adding the
signal there was deemed the simpler solution.

As agreed during bugwash, Martin wants to add back the timeout
as an optinal parameter (default: no timeout).

To override the global parameter on a per-fetch basis.
Signed-off-by: Dridi Boukelmoune <dridi.boukelmoune@gmail.com>

It pauses the fetch progress when clients are lagging behind for
uncacheable streaming deliveries.
Signed-off-by: Dridi Boukelmoune <dridi.boukelmoune@gmail.com>

Signed-off-by: Dridi Boukelmoune <dridi.boukelmoune@gmail.com>

This clarifies which length this field is about.

Better diff with the --word-diff --word-diff-regex='\w+' options.
Signed-off-by: Dridi Boukelmoune <dridi.boukelmoune@gmail.com>

(May not work due to termcap/terminfo differences)

Due to string folding, I expect this change to be fully backwards compatible
- even with std.integert(req.xid) as proven by the vtcs which I am about to
change.

found by flexelint

because we run VRY_Validate() anyway before keeping a vary spec,
and rightly so.

Ref #3858

In dea05fa4, an assertion was added
that, if a vary prediction exists as marked by vary_l, that marker
matches the actual length.

This change uncovered an inconsistency where, for waitinglist returns,
the predictive vary was cleared unconditionally (req->vary_b[2] = '\0'
in VRY_Prep()), but vary_l was not.

Consequently, before dea05fa4,
VRY_Finish() would copy more of the (possibly empty) vary spec
than necessary.

This commit fixes the inconsistency and adds specific testing
for the case.

Fixes #3858

vary, req ttl/grace limits, storage

Motivated by #3858

Refs 8df30240

Fixes #3856