Open n2ygk opened 5 years ago
Using a "proxy+" the path parameter does not get properly substituted, instead passing the parmeter as {proxy+} as in this example URL:
{proxy+}
https://bc28rnvr33.execute-api.us-east-1.amazonaws.com/test/{proxy+}
See attached screenshot.
This appears to be a known issue and is perhaps a problem with AWS API Gateway rather than this portal.
@Team,
Any Update on this issue i am getting the same
Using a "proxy+" the path parameter does not get properly substituted, instead passing the parmeter as
{proxy+}
as in this example URL:https://bc28rnvr33.execute-api.us-east-1.amazonaws.com/test/{proxy+}
See attached screenshot.
This appears to be a known issue and is perhaps a problem with AWS API Gateway rather than this portal.