내용으로 건너뛰기

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

0

I am using Websocket API that uses HTTP integration to communicate with my NodeJS Backend in EC2. I managed to pass on the connectionId on the $connect route using a Request Template.
However when I do this, I am unable to pass on any custom header and querystring parameters. I have tried to pass these values using the Request Template by using the $request.querystring and the $input.params parameters. But this did not work.

When the 'Use HTTP Proxy integration' is checked both the querystring and the custom headers are correctly passed on to the backend, but then the connectionId is not passed on.

My current Request Template is:

{
  "connectionId": "$context.connectionId",
  "domain": "$context.domainName",
  "stage": "$context.stage",
  "requestId": "$context.requestId",
  "body": "$input.body"
}

My question is, if it is possible to pass on querystring parameters/custom headers as well as the connectionId in the $connect route ?

2개 답변
0
수락된 답변

At the time of writing, WebSocket API does not support query strings or headers in the template. You can take a look all supported variables here:
https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-websocket-api-mapping-template-reference.html

I agree that it makes sense to support query strings/headers in the template for the $connect route while it does not for other routes. I'll create a backlog for this.

AWS

답변함 7년 전

전문가

검토됨 2년 전

0

how is this solved? can you share a way to do this right

답변함 2년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

관련 콘텐츠