Skip to content
TheChatArchiveThe Chat Archive
composer-2.5· unknownHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

Untitled conversation

  1. User

    [BUG] API Gateway REST: path-based invocation (/restapis/{id}/{stage}/user_request/{path}) returns 404 After creating a REST API, adding a resource with a Lambda proxy integration, and deploying to a stage, invoking via the documented path format returns "Invalid API id specified" (404).

    Reproduction

    # Create Lambda function
    aws --endpoint-url=http://localhost:4566 lambda create-function \
      --function-name test-fn --runtime nodejs22.x --handler index.handler \
      --role arn:aws:iam::000000000000:role/r \
      --code S3Bucket=...,S3Key=...
    
    # Create REST API + resource + integration + deployment
    API_ID=$(aws --endpoint-url=http://localhost:4566 apigateway create-rest-api --name test | jq -r '.id')
    ROOT_ID=$(aws --endpoint-url=http://localhost:4566 apigateway get-resources --rest-api-id $API_ID | jq -r '.items[0].id')
    RES_ID=$(aws --endpoint-url=http://localhost:4566 apigateway create-resource --rest-api-id $API_ID --parent-id $ROOT_ID --path-part hello | jq -r '.id')
    aws --endpoint-url=http://localhost:4566 apigateway put-method --rest-api-id $API_ID --resource-id $RES_ID --http-method GET --authorization-type NONE
    aws --endpoint-url=http://localhost:4566 apigateway put-integration --rest-api-id $API_ID --resource-id $RES_ID --http-method GET --type AWS_PROXY --integration-http-method POST --uri "arn:aws:apigateway:eu-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:eu-west-2:000000000000:function:test-fn/invocations"
    aws --endpoint-url=http://localhost:4566 apigateway create-deployment --rest-api-id $API_ID --stage-name dev
    
    # Invoke via documented path
    curl http://localhost:4566/restapis/$API_ID/dev/_user_request_/hello
    

    Actual behavior

    HTTP 404: {"message":"Invalid API id specified"}

    Expected behavior

    Request routes through API Gateway to the Lambda function and returns the Lambda response.

    Notes

    • The API is created successfully (confirmed via get-rest-api and Floci logs)
    • The deployment succeeds
    • Management plane operations (create/get/update APIs) all work correctly
    • Only the data plane invocation path fails
    • Tested with Floci 1.5.16

    Environment

    • Floci 1.5.16 (docker.io/floci/floci:latest)
    • Podman 5.8.0 rootless (also likely reproducible with Docker)
    • AWS CLI v2
    • Region: eu-west-2

    Interface

    No new interfaces are introduced.

  2. Assistant

    Investigating how Floci handles API Gateway REST path-based invocations and why they return 404.

  3. Assistant

    Identifying the issue: data-plane requests resolve region from the Authorization header; plain curl defaults to us-east-1 while the API was created in eu-west-2 via AWS CLI. Implementing cross-region API lookup for execute paths and auto-creating stages on create-deployment --stage-name.

  4. Assistant

    Adding an integration test that reproduces the region-mismatch scenario:

  5. Assistant

    Root cause

    The _user_request_ path was reaching the execute controller, but region resolution failed for unauthenticated requests.

    • Management API calls via AWS CLI include a signed Authorization header with the region (eu-west-2 in your repro).
    • Plain curl has no auth header, so RegionResolver falls back to the default region (us-east-1).
    • APIs are stored per-region (eu-west-2::apiId), so the lookup in us-east-1 failed with {"message":"Invalid API id specified"}.

    A second issue in your repro: create-deployment --stage-name dev was not creating the stage in Floci (only the deployment), which would have caused a follow-on Stage not found error after fixing the region issue.

    Fix

    1. Cross-region API lookup on the execute plane — dispatch() now finds REST/HTTP APIs by ID across all regions when the preferred region (from auth or default) does not match.

    2. create-deployment with stageName — REST API deployments now create or update the named stage, matching AWS behavior.

    3. Regression test — ApiGatewayUserRequestRegionIntegrationTest covers creating an API in eu-west-2 via signed requests and invoking it via _user_request_ without an auth header.

    After this fix, your repro should work:

    curl http://localhost:4566/restapis/$API_ID/dev/_user_request_/hello
    

    The same fix also applies to /execute-api/... and /_aws/execute-api/... paths, which had the same region resolution behavior.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.