There are two parts to this: getting them proxying in through tlsproxy correctly, and getting them proxied transitively through varnish layers. Since we're creating open pipes through varnish with this, I'd rather leave it out of the other clusters for now and confine it to cache_misc.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | • chasemp | T1047 Phabricator lacks a "notification" feed similar other project management software: Enable "Flame" | |||
Resolved | • mmodell | T75791 Following Notification from "bell" menu does not clear notification | |||
Resolved | • mmodell | T103444 Desktop notifications | |||
Resolved | • mmodell | T97650 Conpherence wont refresh chat messages automatically, needs manual reload | |||
Resolved | • mmodell | T765 Enable notification server (real-time pop-up notifications) in Phabricator | |||
Resolved | BBlack | T112765 Phabricator needs to expose notification daemon (websocket) | |||
Unknown Object (Task) | |||||
Resolved | Krinkle | T134871 Move stream.wikimedia.org (rcstream) behind cache_misc | |||
Resolved | BBlack | T134870 Support websockets in cache_misc | |||
Declined | BBlack | T107749 HTTP/1.1 keepalive for local nginx->varnish conns |
Event Timeline
Change 287940 had a related patch set uploaded (by BBlack):
tlsproxy: minimize keepalives diff in config
Change 287941 had a related patch set uploaded (by BBlack):
Pipe websockets through traffic layers
Change 287958 had a related patch set uploaded (by BBlack):
cache_misc: turn on websocket support
Change 287995 had a related patch set uploaded (by BBlack):
tlsproxy: switch to (non-persistent) HTTP/1.1
I've merged the first two patches, which are really pre-patches from this ticket's POV. There's some interaction between this work and T107749 , so I'll put the detailed updates about that over there. For now, we're using HTTP/1.1 non-persistent connections via the upstream module for nginx->varnish everywhere, but don't yet have the actual websocket bits merged yet...
Added HTTP/1.1 keepalive task as a blocker. We don't really need keepalives for this, but the work ongoing in that ticket is about resolving the issue with turning on HTTP/1.1 at all (keepalive or not), which is a pre-req for this.
Change 287941 merged by BBlack:
Support optional keepalives and websockets for v4 only
Change 294320 had a related patch set uploaded (by BBlack):
websockets VCL: after HTTPS
Seems to basically work. Ideally we'd limit the websocket VCL capabilities based on req.http.Host as well, but that will have to come later with further refactoring of automated app_directors stuff in T110717