reactive-interaction-gateway

reactive-interaction-gateway copied to clipboard

Currently the validation on valid http methods for the proxy is done during runtime in the api_proxy itself.

This means it's possible to parameterize an endpoint with a certain method (that is actually not supported by the RIG) and you'll only notice, that this is not allowed during the call when you receive an "405 - Method Not Allowed"

For better user experience it would be convenient if you'll receive already an error during parametrization.

Following should be considered:

• The restrictions only apply for target=http (or if target not set -> Defaulted to http)
• No validations should be done for other targets (e.g. kafka or kinesis) as they will take events regardleass of the method
• The validations need to implemented if parametrization is done via environment variable as well as online