Varnish5 builtin VCL without pipe

[Federico Schwindt]

Can you elaborate? How is Upgrade related to OPTIONS?

Also (and this might require more clarifications on the VIP itself),
WebSockets support still requires VCL changes, so we'll be expanding the
changes to vcl_recv{} but either way won't work out of the box.

On Wed, Apr 6, 2016 at 3:54 PM, Dridi Boukelmoune <dridi at varni.sh> wrote:

> On Wed, Apr 6, 2016 at 2:34 PM, Federico Schwindt <fgsch at lodoss.net>
> wrote:
> > For the record, added my comment to the VIP at
> >
> https://github.com/varnishcache/varnish-cache/wiki/VIP8:-No-pipe-in-builtin.vcl-in-V5
> .
>
> Your comment on OPTIONS is valid, but we should also consider protocol
> upgrades. Maybe the test should be if the method is OPTIONS and the
> request contains an Upgrade header field.
>
> Regarding optional upgrades, what happens if the backend responds with 101?
>
> As the VIP says, no matter how pipe turns out in v5, but how does H2
> deal with protocol upgrades? I think it doesn't (eg. websockets)
>
> Dridi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20160406/57a02507/attachment.html>