> That just means that we would have to decompress and recompress > all the streams, in which case we might as well return(pass).
Assuming that pipe would be per-connection, then saying that return(pass) would transmit raw H2 frames directly to the backend (as I understand your comment) would put you in the half pipe situation where you decode some HEADER frames but tunnel others. It's no news that H2 is not very friendly to proxies or tunneling and IMO those were afterthoughts as demonstrated by the expired draft on WS/H2. If you put a proxy between to H2 parties, then the proxy has to maintain 2 HPACK tables with both parties and maintain them as it wishes (except for the never-indexed fields). > No, we can also do transparent piping, for instance based on ACL > matches and similar. I don't understand, are we talking about something like vcl_sess -> vcl_pipe here? Dridi _______________________________________________ varnish-dev mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
