[
https://issues.apache.org/jira/browse/NIFI-15238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-15238:
------------------------------------
Summary: Enforce the value for the HTTP_METHOD property in InvokeHTTP when
not specified as an Expression Language Expression or an arbitrary method
(was: Enforce the value for the HTTP_METHOD property in InvokeHTTP when not
specified as an Expression Language Expression or an Arbitrary Method)
> Enforce the value for the HTTP_METHOD property in InvokeHTTP when not
> specified as an Expression Language Expression or an arbitrary method
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-15238
> URL: https://issues.apache.org/jira/browse/NIFI-15238
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Daniel Stieglitz
> Assignee: Daniel Stieglitz
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The HTTP_METHOD property in InvokeHTTP should only take values GET, POST,
> PUT, PATCH, DELETE, HEAD, OPTIONS or an Expression Language expression. When
> not specified as an Expression Language expression, there is nothing to
> enforce the value is one of GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS.
> The reason partially is that arbitrary methods are supported thereby not
> allowing to validate specific methods.
> This ticket proposes to have users encase arbitrary methods using the the
> Expression Language literal method e.g.
> {code:java}
> ${literal('TRACE')}{code}
> thereby allow for validating when a user enters an HTTP method that it be one
> of GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS and for a pass through when
> a Expression Language expression is used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
