Is it possible to pass variables in a websocket $connect call?

Question

I have some existing code using Tomcat and Grizzly webservers, and they accept a path like the following:

```
wss:///forum/{subject}
```

It doesn't seem possible to configure API Gateway v2 endpoints to have variables such as subject here.  Is that correct or am I missing something?  
  
I realize that I _can_ work around this by sending messages, but it creates an inconsistency from the client perspective and there doesn't seem a good "reason" for it, except it hasn't been done yet.

Accepted Answer

Currently WebSocket API does not support path variables on $connect. You can send query string or custom header (if the client is non-browser) though.

Answer

Thanks.  
  
I wasn't actually able to get the headers approach to work; I'm not sure why, but I only seem to see a subset of the actual headers in the WebSocket lambda.  
  
The query parameters approach worked fine, though.

Is it possible to pass variables in a websocket $connect call?

Relevant questions

Setting up a $connect route that requires a WebSocket subprotocol using a mock integration

Is it possible to use CloudFront Functions with CloudFormation, and have the source code in an external file?

Websocket $connect route: headers and querystring empty on http integration

Trying to use a single Amazon API Gateway endpoint to accept both HTTP and websocket requests

Is possible to set up the BGP pass on a S2S VPN connection

Is it possible to pass variables in a websocket $connect call?

Is it possible to pass a C++ class as a Lua table from a Gem?

Can i access Secrets Manager from Tomcat

Passing a custom message from Websocket API Lambda authroizer to the client

How to retrieve path parameters from websocket url in lambda functions