Skip to content

fix: complete emulator REST APIGatewayProxyRequest and null-safe AspNetCoreServer marshalling - #2567

Open
msmourao wants to merge 1 commit into
aws:masterfrom
msmourao:fix/emulator-incomplete-proxy-request
Open

fix: complete emulator REST APIGatewayProxyRequest and null-safe AspNetCoreServer marshalling#2567
msmourao wants to merge 1 commit into
aws:masterfrom
msmourao:fix/emulator-incomplete-proxy-request

Conversation

@msmourao

Copy link
Copy Markdown

Issue #, if available:
Fixes #2566

Description of changes:
When the Lambda Test Tool v2 API Gateway emulator translates an HTTP request into a REST APIGatewayProxyRequest, it omitted RequestContext and could leave Path / HttpMethod null. Amazon.Lambda.AspNetCoreServer then threw NullReferenceException while marshalling those incomplete events into ASP.NET Core features.

This PR:

  1. Amazon.Lambda.TestTool — populate a minimal RequestContext (and default Path/HttpMethod) for emulator-built REST proxy events, closer to real API Gateway / test-invoke payloads. HTTP API v2 translation already set RequestContext.
  2. Amazon.Lambda.AspNetCoreServer — null-safe marshalling for Path, HttpMethod, path parameters, and header values so incomplete events do not NRE.

Includes an AutoVer change file (Patch) for both projects.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

…er marshalling

API Gateway emulator REST translation omitted RequestContext and could leave Path/HttpMethod null, causing NullReferenceException in Amazon.Lambda.AspNetCoreServer.

Fixes aws#2566

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

API Gateway emulator builds incomplete APIGatewayProxyRequest; AspNetCoreServer NREs on null Path / RequestContext / headers

1 participant