Benjamin Dowson

Also having this issue, are there any fixes for this?

Hi @bentsku, thanks for looking into this for me! I did the curl requests again with the `-H "Accept-Encoding: gzip"` header on the AWS LB and API Gateway, and here...

Hi @bentsku , thanks for the update. I pulled the latest localstack but now I can't import my AWS API: ``` Error importing API Gateway: An error occurred (InternalError) when...

Hi @cloutierMat , deleting the image and repulling it allows me to import again, thanks! @bentsku Now it doesn't seem to detect the created api gateway at all: After I...

Hi @cloutierMat , I just tried with adding the stage name and I still get the same error: ``` curl -v http://421d5aeb.execute-api.localhost.localstack.cloud:4566/local/accounts/health * Trying 127.0.0.1:4566... * TCP_NODELAY set * Connected...

Seems to be: ``` $ awslocal apigatewayv2 get-stage awslocal apigatewayv2 get-stage --api-id 421d5aeb --stage-name local { "CreatedDate": "2024-10-15T06:24:07.439578+00:00", "DefaultRouteSettings": { "DetailedMetricsEnabled": false }, "DeploymentId": "d954f32f", "LastUpdatedDate": "2024-10-15T06:24:07.439578+00:00", "RouteSettings": {}, "StageName":...

Sure, even a trimmed down version of my api json will tell me that it doesnt correspond to a deployed api: ``` { "openapi" : "3.0.1", "info" : { "title"...

Hi @bentsku , after trying it on a fresh VM with the latest version of localstack I am happy to report that it works as expected now when I curl...

@bentsku Yes, it works on the browser now too thanks! It seems postman doesn't output the response headers when there are errors unfortunately, but the headers I get back when...

I tried curl with those headers and it didn't seem to like it: ``` $ curl -H "Accept-Encoding: gzip, deflate, br" -v https://50217dc3.execute-api.localhost.localstack.cloud:4566/local/accounts/health * Trying 127.0.0.1:4566... * TCP_NODELAY set *...