API Gateway TCP response variables not filled in
search cancel

API Gateway TCP response variables not filled in

book

Article ID: 143528

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

After using the "route via HTTPS" assertion the TCP response variables are not available :

  •  ${response.tcp.localIP}
  •  ${response.tcp.remotePort}
  •  ${response.tcp.localPort}
  •  ${response.tcp.localHost}

The TCP request variables are available shows the relevant values from the incoming request :

  • ${request.tcp.remoteIP}
  • ${request.tcp.localIP}
  • ${request.tcp.remotePort}
  • ${request.tcp.localPort}

Environment

All supported versions of the CA API Gateway

Resolution

This is by design, the response TCP variables are currently not supported.