title: Path parameters ignored by AWS API Gateway using proxy+
body: <p>I have a REST API on the AWS API Gateway.  It has one resource, <code>/{proxy+}</code>, that is configured with the <code>ANY</code> method.  The integration request is setup to be a <code>VPC_PROXY</code>, meaning its using a <code>VPC Link</code>.  The VPC link is to a network load balancer that is fronting an app I have running on an ECS cluster using Fargate.</p>
  <p>When using the console's option to test the API, I can confirm that requests are reaching my app but the resource being requested is always <code>/</code> according to my logging.  If I attempt to set the <code>{proxy}</code> value in the method test screen on the console, it seems like my app only ever gets requests for <code>/</code>.  If I set <code>{proxy}</code> to something like <code>widget/5</code>, the response I receive is as if I was request <code>/</code>.</p>
  <p>I'm wondering if there is some way to troubleshoot this, scouring the AWS documentation I can't figure out where I'm going wrong with my setup.</p>