Dridi Boukelmoune

That's because I used `beresp` twice! Good catch!

I force-pushed a clean patch series on top of current master to keep this pull request actionable.

It turns out two test cases were unsetting `resp.http.content-length`, hence the additional force push.

bugwash: @bsdphk to review or implicitly approve by Thursday.

Bugwash: we abandon this idea.

bugwash: let's not break VCL.

We can't predict the length of headers until we decode them. They may be indexed in the session's HPACK dynamic table or compressed using a Huffman tree. I already checked...

This change is made obsolete by plans to move to 64bit VXIDs, but I would like to keep it open until I port it to the 6.0 branch.

We discussed private headers during the last VDD and have a more solid plan relying on header flags instead, we can close this ticket for now. https://github.com/varnishcache/varnish-cache/wiki/VDD23Q1#compliance

All the yak shaving leading to the PoC was merged in https://github.com/varnishcache/varnish-cache/pull/3344.