|
1 | | - |
| 1 | + |
2 | 2 |
|
3 | | -# caddy-lambda |
| 3 | +# caddy-lambda-licious |
4 | 4 |
|
5 | 5 | [Caddy](https://caddyserver.com/) v2 plugin for dispatching requests to [AWS Lambda](https://aws.amazon.com/lambda/). |
6 | 6 |
|
7 | 7 | ## Installation |
8 | 8 |
|
9 | 9 | Use the standard [xcaddy](https://github.com/caddyserver/xcaddy) tool to build a custom `caddy` binary that includes the plugin. |
10 | 10 | ``` |
11 | | -xcaddy build --with github.com/danmoz/caddy-lambda |
| 11 | +xcaddy build --with github.com/danmoz/caddy-lambda-licious |
12 | 12 | ``` |
13 | 13 |
|
14 | 14 | ## Usage |
@@ -47,7 +47,7 @@ By default, the plugin will forward events using the `api_gateway_v2` event form |
47 | 47 | # Recommended for production: assume a dedicated IAM role |
48 | 48 | role_arn arn:aws:iam::123456789012:role/LambdaInvoker |
49 | 49 | external_id example-external-id |
50 | | - session_name caddy-lambda |
| 50 | + session_name caddy-lambda-licious |
51 | 51 |
|
52 | 52 | # Useful for local testing: |
53 | 53 | # endpoint http://127.0.0.1:3001 |
@@ -95,7 +95,7 @@ duplicate invocations. |
95 | 95 |
|
96 | 96 | Be careful when increasing `max_body_size`. AWS Lambda limits synchronous invocation payloads to 6 MB, and this limit applies to the complete serialized event sent to Lambda, not just the HTTP request body. Binary request bodies are base64-encoded, increasing their size by approximately 33%, with headers and the event envelope adding further overhead. |
97 | 97 |
|
98 | | -The default 4 MiB limit leaves some headroom, but unusually large headers may reduce the maximum safe body size. If the serialized Lambda event exceeds the 6 MB limit, caddy-lambda rejects the request with HTTP `413 Payload Too Large`. |
| 98 | +The default 4 MiB limit leaves some headroom, but unusually large headers may reduce the maximum safe body size. If the serialized Lambda event exceeds the 6 MB limit, caddy-lambda-licious rejects the request with HTTP `413 Payload Too Large`. |
99 | 99 |
|
100 | 100 | ## Response Codes |
101 | 101 |
|
@@ -188,7 +188,7 @@ errors, timeouts, throttling, and malformed responses are returned as Caddy |
188 | 188 | handler errors. |
189 | 189 |
|
190 | 190 | Every invocation has a request ID. If the incoming request includes an |
191 | | -`X-Request-ID` header, its value is preserved; otherwise, caddy-lambda |
| 191 | +`X-Request-ID` header, its value is preserved; otherwise, caddy-lambda-licious |
192 | 192 | generates a UUID matching the format used by AWS API Gateway. The request ID |
193 | 193 | is used consistently in `requestContext.requestId` and structured logs, and |
194 | 194 | is returned to the client in the `X-Request-ID` response header. |
|
0 commit comments