AWS apigateway documentation change
Summary
Updated documentation link text from 'Method request behavior for payloads without mapping templates' to 'Integration passthrough behaviors' while maintaining same content about handling unvalidated payloads
Security assessment
Change only modifies terminology and link labels without altering security guidance. No evidence of addressing a specific vulnerability or adding new security features - maintains existing validation behavior documentation.
Diff
diff --git a/apigateway/latest/developerguide/api-gateway-method-request-validation.md b/Users/docs/2025-03-10_15-36-52/apigateway/latest/developerguide/api-gateway-method-request-validation.md index a3a208ced..8f02f5b42 100644 --- a/apigateway/latest/developerguide/api-gateway-method-request-validation.md +++ b/apigateway/latest/developerguide/api-gateway-method-request-validation.md @@ -39 +39 @@ To turn on validation, you specify validation rules in a [request validator](htt -Request body validation and [Method request behavior for payloads without mapping templates for REST APIs in API Gateway](./integration-passthrough-behaviors.html) are two separate topics. When a request payload does not have a matching model schema, you can choose to passthrough or block the original payload. For more information, see [Method request behavior for payloads without mapping templates for REST APIs in API Gateway](./integration-passthrough-behaviors.html). +Request body validation and [Integration passthrough behaviors](./integration-passthrough-behaviors.html) are two separate topics. When a request payload does not have a matching model schema, you can choose to passthrough or block the original payload. For more information, see [Integration passthrough behaviors](./integration-passthrough-behaviors.html).