@emccue Got a chance to start a project, this prints the correct stuff out for me https://gist.github.com/DanielStephens/c3cf076e574afd30fcf48cc9b8bd554e

okay giving it a shot now

hey! that did manage to do something

okay so now I am slightly confused as to what exactly the interceptors are handling if not an http request

but i can work with it now

so what are connection params?

This probably has some inaccuracies but my understanding is, a WebSocket is a protocol that uses multiple http requests, there's one at the start which asks to initialise the connection, the payload passed along with this is what ends up as connection-params as far as I can tell, lacinia.pedestal (by default) just acknowledges this init request as long as it's readable and has the correct upgrade protocol. This seems potentially insecure but you can swap these pieces out with some work I believe. Once that acknowledgement/upgrade cycle has finished, another http request will be made which contains the graphql subscription body that you want to actually listen to. Technically you can send headers on each of those requests but from what I can see it's tricky with the Apollo SubscriptionClient which lacinia uses for GraphiQL. So I think connectionParams are part of the body of the ServletUpgradeRequest, which you managed to get ahold of earlier.

The subscription interceptors handle the bit after the initial connection which contains a graphql subscription body https://github.com/walmartlabs/lacinia-pedestal/blob/master/src/com/walmartlabs/lacinia/pedestal/subscriptions.clj#L151