As we know, you can plug in over 100 middleware handlers from Light in the light-proxy to customize it for your needs. One of the features most users are interested in is the schema validation on the proxy. For example, when you have the OpenAPI 3.0 specification for the backend service, you can deploy the openapi.yaml to the proxy and wire in the openapi-validator to perform the validation against the specification.
For PUT/POST/PATCH requests that pass through the proxy, there are some special configuration considerations.
Before the openapi-validator handler, the body handler must be in the request chain to parse the HTTP body into a JSON object. It will consume the HTTP body stream (need to serialize and deserialize), which is very time-consuming on the proxy. The same stream, of course, will be deserialized on the backend service again for the processing. To avoid this performance issue, we recommend the following configuration.
Don’t plug in the body-parser handler at all in the proxy so that the HTTP stream can be forwarded to the backend service without deserialization and serialization.
Using the handler.yml for the middleware configuration, you can remove the body handler from all the POST/PUT/PATCH paths.
The OpenAPI validation handler will rely on the body handler to parse the request body and won’t work if the body object doesn’t exist in the exchange as an attachment.
To bypass the body validation on the proxy, we can disable the body validation in the openapi-validator.yml
Here is an example for openapi-validator.yml
# Default openapi-validator configuration
# Enable request validation. Response validation is not done on the server but client.
# Log error message if validation error occurs
# Skip body validation set to true if used in light-router, light-proxy and light-spring-boot.
# Enable response validation.
You need to add this config file to your proxy config folder and change the skipBodyValidation to true.
Once the body handler is removed and skipBodyValidation is set to true, the request pass through the proxy will be validated against the specification for headers, query parameters, path parameters but not the request body. With this setup, the backend service will be responsible for validating the body.